Summary: | Ant scripts don't run with a different ANT_HOME | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Matthew Conway <matt> |
Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | ui |
Version: | 2.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Matthew Conway
2002-11-14 19:16:31 EST
Does this happen in your target workspace or the runtime Eclipse IDE? If this is happenning in your target, you may just need to re-build the external tools jars. (i.e run the "buildExtraJAR" in the "scripts" folder of the external tools plug-in. This generates the jars you need at runtime from the development environment. re-assigning as "new" Chalk this one up to user error - it was happening in my runtime workbench
because I hadn't added/built ant.core to the workbench.
Strange thing was, even though I specifically told Window->Preferences->Plugin-
>Platfom to use the built in externaltools plugin, it still used the one in my
workspace until I renamed the plugin.xml. Is that desired behavior? It did
pop up a dialog warning me that it would use the one from the workbench, which
I assumed meant the built in one. If it really meant it would use the
workspace one, then the dialog is confusing and should be re-worded.
|