Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » 3.1RC1 pde build failing

3.1RC1 pde build failing [message #286075]

Wed, 01 June 2005 17:03

Eclipse User

I have an ant based headless build that I created from the pde-build scripts
using map definitions and such. It looks like the new configuration of plugins
as jars rather than directories is confusing it.

I get:
....pde-build/genericTargets.xml:64: org.eclipse.core.runtime.CoreException:
Unable to find plug-in: org.eclipse.update.configurator_3.0.0. Please check the
error log for more details.

I can't find anything referring to 3.0.0 specifically, though I do specify the
configurator plugin in a couple of places. Can anyone tell me what has changed?

Also, anybody have any updated docs for the 'right way' to do headless builds in
3.1?

Chris

Re: 3.1RC1 pde build failing [message #286077 is a reply to message #286075]

Wed, 01 June 2005 18:20

Eclipse User

Usually this is an indication that either that plugin or one of that plugins
dependencies is missing from the plugin model.
Usually the missing plugins are listed at the top of the error log

HTH
Darins

"Chris Longfield" <clongfield@internap.com> wrote in message
news:d7l867$ga1$1@news.eclipse.org...
>I have an ant based headless build that I created from the pde-build
>scripts using map definitions and such. It looks like the new
>configuration of plugins as jars rather than directories is confusing it.
>
> I get:
> ...pde-build/genericTargets.xml:64:
> org.eclipse.core.runtime.CoreException: Unable to find plug-in:
> org.eclipse.update.configurator_3.0.0. Please check the error log for more
> details.
>
> I can't find anything referring to 3.0.0 specifically, though I do specify
> the configurator plugin in a couple of places. Can anyone tell me what
> has changed?
>
> Also, anybody have any updated docs for the 'right way' to do headless
> builds in 3.1?
>
> Chris

Re: 3.1RC1 pde build failing [message #286104 is a reply to message #286077]

Thu, 02 June 2005 11:57

Eclipse User

Yeah, it's weird because that plugin, well, the 3.1 version, does exist
as a jar in the plugins directory. This is not some problem with it
being a jar, is it? Why might it think it needs 3.0.0 instead of the
3.1.0 that is there? Where does this error log get written when I am
running headless ( -Dbuilder=. )?

Chris

Darin Swanson wrote:
> Usually this is an indication that either that plugin or one of that plugins
> dependencies is missing from the plugin model.
> Usually the missing plugins are listed at the top of the error log
>
> HTH
> Darins
>
> "Chris Longfield" <clongfield@internap.com> wrote in message
> news:d7l867$ga1$1@news.eclipse.org...
>
>>I have an ant based headless build that I created from the pde-build
>>scripts using map definitions and such. It looks like the new
>>configuration of plugins as jars rather than directories is confusing it.
>>
>>I get:
>>...pde-build/genericTargets.xml:64:
>>org.eclipse.core.runtime.CoreException: Unable to find plug-in:
>>org.eclipse.update.configurator_3.0.0. Please check the error log for more
>>details.
>>
>>I can't find anything referring to 3.0.0 specifically, though I do specify
>>the configurator plugin in a couple of places. Can anyone tell me what
>>has changed?
>>
>>Also, anybody have any updated docs for the 'right way' to do headless
>>builds in 3.1?
>>
>>Chris
>
>
>

Re: 3.1RC1 pde build failing [message #286108 is a reply to message #286104]

Thu, 02 June 2005 12:59

Eclipse User

> Darin Swanson wrote:
>
>> Usually this is an indication that either that plugin or one of that
>> plugins dependencies is missing from the plugin model.
>> Usually the missing plugins are listed at the top of the error log
>>
>> HTH

The extra details are that it is getting an InvocationTargetException
caused by its inablity to find the org.eclipse.update.configurator_3.0.0
plugin. I guess my question now is, how can I figure out who is asking
for this specific plugin (as opposed to the
org.eclipse.update.configurator_3.1.0 plugin which *is* there ) ?

I mean, I think the missing plugin reallly is the
org.eclipse.update.configurator_3.0.0 plugin. It just doesn't make
sense that it should be looking for this one.

Chris

---------------
stack:
!SESSION 2005-06-02 12:40:42.553
-----------------------------------------------
eclipse.buildId=I20050527-1300
java.version=1.4.2_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -application org.eclipse.ant.core.antRunner
-Dbuilder=. -Dbuild.compiler=modern
Command-line arguments: -application org.eclipse.ant.core.antRunner
-data workspace_data -Dbuilder=. -Dbuild.compiler=modern

!ENTRY org.eclipse.osgi 2005-06-02 12:40:52.156
!MESSAGE Application error
!STACK 1
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:494)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:375)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: /usr/opt/ws/miro/ui/pde-build/build.xml:22: The following
error occurred while executing this line:
/usr/opt/ws/miro/ui/pde-build/build.xml:76: The following error occurred
while executing this line:
/usr/opt/ws/miro/ui/pde-build/customTargets.xml:10: The following error
occurred while executing this line:
/usr/opt/ws/miro/ui/pde-build/genericTargets.xml:64:
org.eclipse.core.runtime.CoreException: Unable to find plug-in:
org.eclipse.update.configurator_3.0.0. Please check the error log for
more details.
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget. java:107)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:704)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:582)
... 16 more

Re: 3.1RC1 pde build failing [message #286113 is a reply to message #286108]

Thu, 02 June 2005 13:22

Eclipse User

> The extra details are that it is getting an InvocationTargetException
> caused by its inablity to find the org.eclipse.update.configurator_3.0.0
> plugin. I guess my question now is, how can I figure out who is asking
> for this specific plugin (as opposed to the
> org.eclipse.update.configurator_3.1.0 plugin which *is* there ) ?
>
> I mean, I think the missing plugin reallly is the
> org.eclipse.update.configurator_3.0.0 plugin. It just doesn't make
> sense that it should be looking for this one.
>

Aha:
my rcp helper feature.xml really DID ask for it:

....<plugin
id="org.eclipse.update.configurator"
download-size="0"
install-size="0"
version="3.0.0"/>...

instead of

....<plugin
id="org.eclipse.update.configurator"
download-size="0"
install-size="0"
version="0.0.0"/>...

like all my other plugins that I pull in.

Previous Topic:	How does one get an Eclipse bug fixed when you have provided a solution in Bugzilla?
Next Topic:	Key binding for terminate - works 3.0, not 3.1

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 20:10:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter