Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Adding source feature causes MissingComponentException in site.p2.zip action
Adding source feature causes MissingComponentException in site.p2.zip action [message #629681] Wed, 29 September 2010 04:47 Go to next message
Michael Wenz is currently offline Michael Wenz
Messages: 1590
Registered: July 2009
Location: Walldorf, Germany
Senior Member
Hi,

when I try to build my update site via the site.p2.zip action and have added
the source features that are produced by Buckminster automatically to my SDK
feature the build fails with:
ERROR: org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
component named org.eclipse.graphiti.feature.examples.source:eclipse.feature
is known to Buckminster
org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
component named org.eclipse.graphiti.feature.examples.source:eclipse.feature
is known to Buckminster
at
org.eclipse.buckminster.core.metadata.WorkspaceInfo.resolveL ocal(WorkspaceInfo.java:624)
at
org.eclipse.buckminster.core.metadata.WorkspaceInfo.getResol ution(WorkspaceInfo.java:519)
at
org.eclipse.buckminster.core.metadata.ModelCache.findCSpec(M odelCache.java:46)
at
org.eclipse.buckminster.core.internal.actor.PerformContext.f indCSpec(PerformContext.java:219)
at
org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced CSpec(CSpec.java:461)
at
org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced Attribute(CSpec.java:439)
at
org.eclipse.buckminster.core.cspec.model.Prerequisite.getRef erencedAttribute(Prerequisite.java:142)
at
org.eclipse.buckminster.core.cspec.model.Group.internalGetPa thGroups(Group.java:205)
at
org.eclipse.buckminster.core.cspec.model.TopLevelAttribute.g etPathGroups(TopLevelAttribute.java:176)
at
org.eclipse.buckminster.core.internal.actor.PerformContext.a ddPrerequisitePathGroups(PerformContext.java:164)
at
org.eclipse.buckminster.core.internal.actor.PerformContext.g etNamedPathGroupArrays(PerformContext.java:276)
at
org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:238)
at
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:186)
at
org.eclipse.buckminster.core.internal.actor.PerformManager$D irectActionInvocation.execute(PerformManager.java:143)
at
org.eclipse.buckminster.core.internal.actor.PerformManager.i nternalPerform(PerformManager.java:454)
at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:293)
at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:305)
at
org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:108)
at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:91)
at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:194)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 17)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 36)
at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :156)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:369)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
No component named
org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
Buckminster
I have the follwing feature structure:
org.eclipse.graphiti.site -> org.eclipse.graphiti.feature
->
org.eclipse.graphiti.feature.examples
->
..graphiti.sdk.feature -> org.eclipse.graphiti.feature

-> org.eclipse.graphiti.feature.examples

-> org.eclipse.graphiti.source.feature

-> org.eclipse.graphiti.feature.examples.source

When I check my Hudson workspace both source feature appear in the Hudson
build folder.

Here are the links to my build log:
With sources added it fails:
https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 82/console
Without sources it runs through:
https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 81/console

What am I missing?

Thanks,
Michael
Re: Adding source feature causes MissingComponentException in site.p2.zip action [message #630027 is a reply to message #629681] Thu, 30 September 2010 08:18 Go to previous messageGo to next message
Michael Wenz is currently offline Michael Wenz
Messages: 1590
Registered: July 2009
Location: Walldorf, Germany
Senior Member
I did some more investigations on this and found a strange behavior in
Buckminster: depending on the sequence of my feature includes the build
succeeds or fails.

We have two main features, let's call them feature and feature.examples. For
both obviously source features exist: feature.source and examples.source.

Besides there is our SDK feature consisting of all 4 features from above
(convenience for downloading).

If I now define the my site feature (the one that is being built using
Buckminster's site.p2 action) in different sequences the build succeeds or
fails:
Success: SDK.feature, feature, feature.examples
Failure: feature, feature.examples, SDK.feature

Is this exspected behavior or a bug or does this somehow depend on any other
configuration setting?

-Michael


"Michael Wenz" <michael.wenz@sap.com> wrote in message
news:i7uu87$us5$1@news.eclipse.org...
> Hi,
>
> when I try to build my update site via the site.p2.zip action and have
> added the source features that are produced by Buckminster automatically
> to my SDK feature the build fails with:
> ERROR: org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
> component named
> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
> Buckminster
> org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
> component named
> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
> Buckminster
> at
> org.eclipse.buckminster.core.metadata.WorkspaceInfo.resolveL ocal(WorkspaceInfo.java:624)
> at
> org.eclipse.buckminster.core.metadata.WorkspaceInfo.getResol ution(WorkspaceInfo.java:519)
> at
> org.eclipse.buckminster.core.metadata.ModelCache.findCSpec(M odelCache.java:46)
> at
> org.eclipse.buckminster.core.internal.actor.PerformContext.f indCSpec(PerformContext.java:219)
> at
> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced CSpec(CSpec.java:461)
> at
> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced Attribute(CSpec.java:439)
> at
> org.eclipse.buckminster.core.cspec.model.Prerequisite.getRef erencedAttribute(Prerequisite.java:142)
> at
> org.eclipse.buckminster.core.cspec.model.Group.internalGetPa thGroups(Group.java:205)
> at
> org.eclipse.buckminster.core.cspec.model.TopLevelAttribute.g etPathGroups(TopLevelAttribute.java:176)
> at
> org.eclipse.buckminster.core.internal.actor.PerformContext.a ddPrerequisitePathGroups(PerformContext.java:164)
> at
> org.eclipse.buckminster.core.internal.actor.PerformContext.g etNamedPathGroupArrays(PerformContext.java:276)
> at
> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:238)
> at
> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:186)
> at
> org.eclipse.buckminster.core.internal.actor.PerformManager$D irectActionInvocation.execute(PerformManager.java:143)
> at
> org.eclipse.buckminster.core.internal.actor.PerformManager.i nternalPerform(PerformManager.java:454)
> at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:293)
> at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:305)
> at
> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:108)
> at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:91)
> at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:194)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 17)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 36)
> at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :156)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:196)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:369)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
> No component named
> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
> Buckminster
> I have the follwing feature structure:
> org.eclipse.graphiti.site -> org.eclipse.graphiti.feature
> ->
> org.eclipse.graphiti.feature.examples
> ->
> dk.feature -> org.eclipse.graphiti.feature
>
> -> org.eclipse.graphiti.feature.examples
>
> -> org.eclipse.graphiti.source.feature
>
> -> org.eclipse.graphiti.feature.examples.source
>
> When I check my Hudson workspace both source feature appear in the Hudson
> build folder.
>
> Here are the links to my build log:
> With sources added it fails:
> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 82/console
> Without sources it runs through:
> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 81/console
>
> What am I missing?
>
> Thanks,
> Michael
>
>
Re: Adding source feature causes MissingComponentException in site.p2.zip action [message #630029 is a reply to message #630027] Thu, 30 September 2010 08:27 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Please report this in a bugzilla. It's worth a lot if you can provide a
sample that reproduces the problem.

- thomas

On 09/30/2010 02:18 PM, Michael Wenz wrote:
> I did some more investigations on this and found a strange behavior in
> Buckminster: depending on the sequence of my feature includes the build
> succeeds or fails.
>
> We have two main features, let's call them feature and feature.examples. For
> both obviously source features exist: feature.source and examples.source.
>
> Besides there is our SDK feature consisting of all 4 features from above
> (convenience for downloading).
>
> If I now define the my site feature (the one that is being built using
> Buckminster's site.p2 action) in different sequences the build succeeds or
> fails:
> Success: SDK.feature, feature, feature.examples
> Failure: feature, feature.examples, SDK.feature
>
> Is this exspected behavior or a bug or does this somehow depend on any other
> configuration setting?
>
> -Michael
>
>
> "Michael Wenz"<michael.wenz@sap.com> wrote in message
> news:i7uu87$us5$1@news.eclipse.org...
>> Hi,
>>
>> when I try to build my update site via the site.p2.zip action and have
>> added the source features that are produced by Buckminster automatically
>> to my SDK feature the build fails with:
>> ERROR: org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
>> component named
>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>> Buckminster
>> org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
>> component named
>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>> Buckminster
>> at
>> org.eclipse.buckminster.core.metadata.WorkspaceInfo.resolveL ocal(WorkspaceInfo.java:624)
>> at
>> org.eclipse.buckminster.core.metadata.WorkspaceInfo.getResol ution(WorkspaceInfo.java:519)
>> at
>> org.eclipse.buckminster.core.metadata.ModelCache.findCSpec(M odelCache.java:46)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformContext.f indCSpec(PerformContext.java:219)
>> at
>> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced CSpec(CSpec.java:461)
>> at
>> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced Attribute(CSpec.java:439)
>> at
>> org.eclipse.buckminster.core.cspec.model.Prerequisite.getRef erencedAttribute(Prerequisite.java:142)
>> at
>> org.eclipse.buckminster.core.cspec.model.Group.internalGetPa thGroups(Group.java:205)
>> at
>> org.eclipse.buckminster.core.cspec.model.TopLevelAttribute.g etPathGroups(TopLevelAttribute.java:176)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformContext.a ddPrerequisitePathGroups(PerformContext.java:164)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformContext.g etNamedPathGroupArrays(PerformContext.java:276)
>> at
>> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:238)
>> at
>> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:186)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformManager$D irectActionInvocation.execute(PerformManager.java:143)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformManager.i nternalPerform(PerformManager.java:454)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:293)
>> at
>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:305)
>> at
>> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:108)
>> at
>> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:91)
>> at
>> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:194)
>> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 17)
>> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 36)
>> at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :156)
>> at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:196)
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:369)
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>> 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:597)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
>> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
>> No component named
>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>> Buckminster
>> I have the follwing feature structure:
>> org.eclipse.graphiti.site -> org.eclipse.graphiti.feature
>> ->
>> org.eclipse.graphiti.feature.examples
>> ->
>> dk.feature -> org.eclipse.graphiti.feature
>>
>> -> org.eclipse.graphiti.feature.examples
>>
>> -> org.eclipse.graphiti.source.feature
>>
>> -> org.eclipse.graphiti.feature.examples.source
>>
>> When I check my Hudson workspace both source feature appear in the Hudson
>> build folder.
>>
>> Here are the links to my build log:
>> With sources added it fails:
>> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 82/console
>> Without sources it runs through:
>> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 81/console
>>
>> What am I missing?
>>
>> Thanks,
>> Michael
>>
>>
>
>
Re: Adding source feature causes MissingComponentException in site.p2.zip action [message #630277 is a reply to message #630029] Fri, 01 October 2010 07:22 Go to previous message
Michael Wenz is currently offline Michael Wenz
Messages: 1590
Registered: July 2009
Location: Walldorf, Germany
Senior Member
Done.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=326764



Michael



"Thomas Hallgren" <thomas@tada.se> wrote in message
news:i81vhv$ds3$1@news.eclipse.org...
> Please report this in a bugzilla. It's worth a lot if you can provide a
> sample that reproduces the problem.
>
> - thomas
>
> On 09/30/2010 02:18 PM, Michael Wenz wrote:
>> I did some more investigations on this and found a strange behavior in
>> Buckminster: depending on the sequence of my feature includes the build
>> succeeds or fails.
>>
>> We have two main features, let's call them feature and feature.examples.
>> For
>> both obviously source features exist: feature.source and examples.source.
>>
>> Besides there is our SDK feature consisting of all 4 features from above
>> (convenience for downloading).
>>
>> If I now define the my site feature (the one that is being built using
>> Buckminster's site.p2 action) in different sequences the build succeeds
>> or
>> fails:
>> Success: SDK.feature, feature, feature.examples
>> Failure: feature, feature.examples, SDK.feature
>>
>> Is this exspected behavior or a bug or does this somehow depend on any
>> other
>> configuration setting?
>>
>> -Michael
>>
>>
>> "Michael Wenz"<michael.wenz@sap.com> wrote in message
>> news:i7uu87$us5$1@news.eclipse.org...
>>> Hi,
>>>
>>> when I try to build my update site via the site.p2.zip action and have
>>> added the source features that are produced by Buckminster automatically
>>> to my SDK feature the build fails with:
>>> ERROR: org.eclipse.buckminster.core.metadata.MissingComponentExcept ion:
>>> No
>>> component named
>>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>>> Buckminster
>>> org.eclipse.buckminster.core.metadata.MissingComponentExcept ion: No
>>> component named
>>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>>> Buckminster
>>> at
>>> org.eclipse.buckminster.core.metadata.WorkspaceInfo.resolveL ocal(WorkspaceInfo.java:624)
>>> at
>>> org.eclipse.buckminster.core.metadata.WorkspaceInfo.getResol ution(WorkspaceInfo.java:519)
>>> at
>>> org.eclipse.buckminster.core.metadata.ModelCache.findCSpec(M odelCache.java:46)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformContext.f indCSpec(PerformContext.java:219)
>>> at
>>> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced CSpec(CSpec.java:461)
>>> at
>>> org.eclipse.buckminster.core.cspec.model.CSpec.getReferenced Attribute(CSpec.java:439)
>>> at
>>> org.eclipse.buckminster.core.cspec.model.Prerequisite.getRef erencedAttribute(Prerequisite.java:142)
>>> at
>>> org.eclipse.buckminster.core.cspec.model.Group.internalGetPa thGroups(Group.java:205)
>>> at
>>> org.eclipse.buckminster.core.cspec.model.TopLevelAttribute.g etPathGroups(TopLevelAttribute.java:176)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformContext.a ddPrerequisitePathGroups(PerformContext.java:164)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformContext.g etNamedPathGroupArrays(PerformContext.java:276)
>>> at
>>> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:238)
>>> at
>>> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:186)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformManager$D irectActionInvocation.execute(PerformManager.java:143)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformManager.i nternalPerform(PerformManager.java:454)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:293)
>>> at
>>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:305)
>>> at
>>> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:108)
>>> at
>>> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:91)
>>> at
>>> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:194)
>>> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 17)
>>> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 36)
>>> at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :156)
>>> at
>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:196)
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:369)
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>> 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:597)
>>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
>>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
>>> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
>>> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
>>> No component named
>>> org.eclipse.graphiti.feature.examples.source:eclipse.feature is known to
>>> Buckminster
>>> I have the follwing feature structure:
>>> org.eclipse.graphiti.site -> org.eclipse.graphiti.feature
>>> ->
>>> org.eclipse.graphiti.feature.examples
>>> ->
>>> dk.feature -> org.eclipse.graphiti.feature
>>>
>>> -> org.eclipse.graphiti.feature.examples
>>>
>>> -> org.eclipse.graphiti.source.feature
>>>
>>> -> org.eclipse.graphiti.feature.examples.source
>>>
>>> When I check my Hudson workspace both source feature appear in the
>>> Hudson
>>> build folder.
>>>
>>> Here are the links to my build log:
>>> With sources added it fails:
>>> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 82/console
>>> Without sources it runs through:
>>> https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/3 81/console
>>>
>>> What am I missing?
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>
>>
>
Previous Topic:The project cannot be built until its prerequisite org.eclipse.ui is built.
Next Topic:Resource .buckminster/tp is not local
Goto Forum:
  


Current Time: Fri Aug 29 20:32:59 EDT 2014

Powered by FUDForum. Page generated in 0.08829 seconds