| Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #49469] |
Thu, 05 March 2009 17:47  |
Eclipse User |
|
|
|
I am testing our setup using 3.5M5 and have encountered a problem with
running a contributed ant task in headless mode.
We have a plug-in that contributes an Ant task to the IDE using the
org.eclipse.core.antTasks extension. This Ant task is used by an Ant script
that is executed by running Eclipse in headless mode. The script is launched
from within the IDE and the same Eclipse installation is used to run in
headless mode.
This is working in Eclipse 3.3.2, but in Eclipse 3.5M5 the script fails
because the Ant task is not defined to the headless instance. This only
occurs on the first execution of the 3.5M5 IDE after adding the plug-in to
the dropins folder. If I restart the 3.5M5 IDE and re-run the script it all
works as expected.
Any ideas?
Namaste, Bruce
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #49499 is a reply to message #49469] |
Thu, 05 March 2009 18:12  |
| Eclipse User |
|
|
|
Bruce Kelly wrote:
> I am testing our setup using 3.5M5 and have encountered a problem with
> running a contributed ant task in headless mode.
>
> We have a plug-in that contributes an Ant task to the IDE using the
> org.eclipse.core.antTasks extension. This Ant task is used by an Ant script
> that is executed by running Eclipse in headless mode. The script is launched
> from within the IDE and the same Eclipse installation is used to run in
> headless mode.
>
> This is working in Eclipse 3.3.2, but in Eclipse 3.5M5 the script fails
> because the Ant task is not defined to the headless instance. This only
> occurs on the first execution of the 3.5M5 IDE after adding the plug-in to
> the dropins folder. If I restart the 3.5M5 IDE and re-run the script it all
> works as expected.
>
> Any ideas?
I assume this happens because what PDE is doing is reading what's
installed into your IDE (i.e., it's checking the bundles.info file from
p2). When you just drop it in, PDE isn't aware of the new bundle yet and
it doesn't add it to the PDE state. When you restart, this gets picked
up, added to the bundles.info by p2, and PDE becomes happy. Do you
actually see the bundle in your target when you add it the first time?
If it's not there, of course it isn't going to work :o
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #50406 is a reply to message #49499] |
Sun, 15 March 2009 23:21 |
| Eclipse User |
|
|
|
>
> I assume this happens because what PDE is doing is reading what's
> installed into your IDE (i.e., it's checking the bundles.info file from
> p2). When you just drop it in, PDE isn't aware of the new bundle yet and
> it doesn't add it to the PDE state. When you restart, this gets picked up,
> added to the bundles.info by p2, and PDE becomes happy. Do you actually
> see the bundle in your target when you add it the first time? If it's not
> there, of course it isn't going to work :o
>
On all but one attempt it showed in both the plugin registry view and the
plugins view. In the one attempt that was different, it showed up in the
plugin registry view but *not* the plugins view. Weird.
I have just installed 3.5M6 so I will retest to see if it still happens.
Namaste, Bruce
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #50546 is a reply to message #50406] |
Mon, 16 March 2009 16:57 |
| Eclipse User |
|
|
|
>
> I have just installed 3.5M6 so I will retest to see if it still happens.
>
The process I followed was to unzip the Eclipse Classic file, update the
eclipse.ini file to set the system property
org.eclipse.equinox.p2.reconciler.dropins.directory to point to our
extensions and start Eclipse.
The plug-in providing the Ant task shows in the plug-ins view but the job
running the same Eclipse installation in headless mode fails because the
task name is not defined. The job is run using a launch configuration
created by a locally developed plug-in.
Restart Eclipse and re-run the same job. It now works as expected.
Restart Eclipse with the -clean option and the problem re-appears.
I'm guessing that there is some persistent information that is not being
written out until Eclipse is shutdown.
Namaste, Bruce
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #592859 is a reply to message #49469] |
Thu, 05 March 2009 18:12 |
| Eclipse User |
|
|
|
Bruce Kelly wrote:
> I am testing our setup using 3.5M5 and have encountered a problem with
> running a contributed ant task in headless mode.
>
> We have a plug-in that contributes an Ant task to the IDE using the
> org.eclipse.core.antTasks extension. This Ant task is used by an Ant script
> that is executed by running Eclipse in headless mode. The script is launched
> from within the IDE and the same Eclipse installation is used to run in
> headless mode.
>
> This is working in Eclipse 3.3.2, but in Eclipse 3.5M5 the script fails
> because the Ant task is not defined to the headless instance. This only
> occurs on the first execution of the 3.5M5 IDE after adding the plug-in to
> the dropins folder. If I restart the 3.5M5 IDE and re-run the script it all
> works as expected.
>
> Any ideas?
I assume this happens because what PDE is doing is reading what's
installed into your IDE (i.e., it's checking the bundles.info file from
p2). When you just drop it in, PDE isn't aware of the new bundle yet and
it doesn't add it to the PDE state. When you restart, this gets picked
up, added to the bundles.info by p2, and PDE becomes happy. Do you
actually see the bundle in your target when you add it the first time?
If it's not there, of course it isn't going to work :o
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #593209 is a reply to message #49499] |
Sun, 15 March 2009 23:21 |
| Eclipse User |
|
|
|
>
> I assume this happens because what PDE is doing is reading what's
> installed into your IDE (i.e., it's checking the bundles.info file from
> p2). When you just drop it in, PDE isn't aware of the new bundle yet and
> it doesn't add it to the PDE state. When you restart, this gets picked up,
> added to the bundles.info by p2, and PDE becomes happy. Do you actually
> see the bundle in your target when you add it the first time? If it's not
> there, of course it isn't going to work :o
>
On all but one attempt it showed in both the plugin registry view and the
plugins view. In the one attempt that was different, it showed up in the
plugin registry view but *not* the plugins view. Weird.
I have just installed 3.5M6 so I will retest to see if it still happens.
Namaste, Bruce
|
|
|
| Re: Contributed Ant task, headless behaviour changed 3.3.2 -> 3.5M5 [message #593253 is a reply to message #50406] |
Mon, 16 March 2009 16:57 |
| Eclipse User |
|
|
|
>
> I have just installed 3.5M6 so I will retest to see if it still happens.
>
The process I followed was to unzip the Eclipse Classic file, update the
eclipse.ini file to set the system property
org.eclipse.equinox.p2.reconciler.dropins.directory to point to our
extensions and start Eclipse.
The plug-in providing the Ant task shows in the plug-ins view but the job
running the same Eclipse installation in headless mode fails because the
task name is not defined. The job is run using a launch configuration
created by a locally developed plug-in.
Restart Eclipse and re-run the same job. It now works as expected.
Restart Eclipse with the -clean option and the problem re-appears.
I'm guessing that there is some persistent information that is not being
written out until Eclipse is shutdown.
Namaste, Bruce
|
|
|
Powered by
FUDForum. Page generated in 0.04187 seconds
Home