Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Build fails after headless resolve using p2
Build fails after headless resolve using p2 [message #436288] Thu, 30 July 2009 22:55 Go to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Hi All,

I'm doing a headless build, as described in the "test" target at the end
of the following ant script:

http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu .uci.isr.infrastructure.buckminster_build_test/build.xml

During the resolve step, I can resolve everything using a simple cquery,
which places the dependent "org.eclipse.emf" plugin in the workspace. But,
then when I build the workspace in the command following the resolve, I
get an error:

Error: file
C:\Users\scott\eclipse\workspaces\buck-test\edu.uci.isr.infr astructure.buckminster_build_test\temp\buckminster\workspace \plugins\org.eclipse.emf:
build.properties does not exist

If I instead resolve using the alternative mspec in the ant script, the
"org.eclipse.emf" plugin is placed in buckminster's plugin's folder, and
the build fails because of the following error:

Error: file
C:\Users\scott\eclipse\workspaces\buck-test\edu.uci.isr.infr astructure.buckminster_build_test\temp\buckminster\workspace \plugins\edu.uci.isr.infrastructure.project_requiring_emf\ME TA-INF\MANIFEST.MF,
line 7: Bundle 'org.eclipse.emf' cannot be resolved

What I'd like to have happen is for the "org.eclipse.emf" plugin to be
placed in the target platform. But, I'm not sure how to do that. Any ideas?

Thank you,
-- Scott
Re: Build fails after headless resolve using p2 [message #468274 is a reply to message #436288] Tue, 04 August 2009 18:51 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Any suggestions? Is anyone else able to successfully perform this build
(note: this is very small. It checks out a feature, which includes a
single prodjct, which depends on org.eclipse.emf). I'll include the
relevant files, below, in case that helps anyone in figuring out what's
going on.

I made the ant build script so that it would be easy for someone else to
see what I'm doing and reproduce the error. I hope it helps!

Thank you,
-- Scott

------------------------------ Target Platform:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.5"?>

<target name="Eclipse SDK with delta pack">
<locations>
<location includeAllPlatforms="true" includeMode="slicer"
type="InstallableUnit">
<unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
<repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
</location>
</locations>
</target>

------------------------------ MSPEC:

<?xml version="1.0" encoding="UTF-8"?>
<md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
name="workspace materializer by default, P2 otherwise"
shortDesc="update_site_workspace_p2"
materializer="workspace"
conflictResolution="UPDATE"
url="./update_site.cquery" >
<md:property key="eclipse.version" value="3.4"/>
<md:mspecNode namePattern="^org\.eclipse(\.[^\.]+)*$" materializer="p2"
conflictResolution="UPDATE" />
</md:mspec>

------------------------------ CQUERY:

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
<cq:rootRequest
name="edu.uci.isr.infrastructure.update_site_with_feature"
componentType="buckminster"/>
<cq:property key="eclipse.version" value="3.4"/>
<cq:advisorNode namePattern="^edu\.uci\.isr\..*$"
useTargetPlatform="false" branchTagPath="main"/>
</cq:componentQuery>

------------------------------ Result from build:

"Error: file
C:\Users\scott\eclipse\workspaces\buck-test\edu.uci.isr.infr astructure.buckminster_build_test\temp\buckminster\workspace \plugins\edu.uci.isr.infrastructure.project_requiring_emf\ME TA-INF\MANIFEST.MF,
line 7: Bundle 'org.eclipse.emf' cannot be resolved"

------------------------------ Result from running the action (and
skipping the build):

${sp:manifest} is undefined
Re: Build fails after headless resolve using p2 [message #468344 is a reply to message #468274] Wed, 05 August 2009 07:49 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Scott,
You don't have any installLocation set for your p2 materializer so you probably hit what's described here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=285449

You can try the following:
1. Create an empty folder that will be the destination for the things you want to materialize into your TP.
2. Add this folder as a "Directory" to your active TP.

That should do the trick.

HTH,
Thomas Hallgren


Scott Hendrickson wrote:
> Any suggestions? Is anyone else able to successfully perform this build
> (note: this is very small. It checks out a feature, which includes a
> single prodjct, which depends on org.eclipse.emf). I'll include the
> relevant files, below, in case that helps anyone in figuring out what's
> going on.
>
> I made the ant build script so that it would be easy for someone else to
> see what I'm doing and reproduce the error. I hope it helps!
>
> Thank you,
> -- Scott
>
> ------------------------------ Target Platform:
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <?pde version="3.5"?>
>
> <target name="Eclipse SDK with delta pack">
> <locations>
> <location includeAllPlatforms="true" includeMode="slicer"
> type="InstallableUnit">
> <unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
> <repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
> </location>
> </locations>
> </target>
>
> ------------------------------ MSPEC:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
> name="workspace materializer by default, P2 otherwise"
> shortDesc="update_site_workspace_p2"
> materializer="workspace"
> conflictResolution="UPDATE"
> url="./update_site.cquery" >
> <md:property key="eclipse.version" value="3.4"/>
> <md:mspecNode namePattern="^org\.eclipse(\.[^\.]+)*$"
> materializer="p2" conflictResolution="UPDATE" />
> </md:mspec>
>
> ------------------------------ CQUERY:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <cq:componentQuery
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
> resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
>
> <cq:rootRequest
> name="edu.uci.isr.infrastructure.update_site_with_feature"
> componentType="buckminster"/>
> <cq:property key="eclipse.version" value="3.4"/>
> <cq:advisorNode namePattern="^edu\.uci\.isr\..*$"
> useTargetPlatform="false" branchTagPath="main"/>
> </cq:componentQuery>
>
> ------------------------------ Result from build:
>
> "Error: file
> C:\Users\scott\eclipse\workspaces\buck-test\edu.uci.isr.infr astructure.buckminster_build_test\temp\buckminster\workspace \plugins\edu.uci.isr.infrastructure.project_requiring_emf\ME TA-INF\MANIFEST.MF,
> line 7: Bundle 'org.eclipse.emf' cannot be resolved"
>
> ------------------------------ Result from running the action (and
> skipping the build):
>
> ${sp:manifest} is undefined
>
>
>
Re: Build fails after headless resolve using p2 [message #470843 is a reply to message #468344] Wed, 05 August 2009 18:25 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Hi Thomas,

Thanks for your response. I've done as you suggested and the
org.eclipse.emf plugin is now placed in a "target" folder that I've added
to the target platform definition. However, when I still get the following
error:

1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
doesn't exist (details below: [1])

NOTE: I updated the build script to insert the local path manually for the
location using an xstl.

I also noticed that when I execute a lsprefs command, I now get the
following exception:

2) "Active target 'Eclipse SDK with delta pack' is too complex to be
represented by a single path" (details below: [2]). This should probably
report the issue, but not throw an exception - halting the process.

The second issue is not a show stopper, I just commented out these
commands. But, I'm not sure what to do to fix the fist issue.

The update site's buckminster.cspec was created using the instructions
here:
http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster
So, I think I have everything in there (and this used to work), but I'm
not sure what I need to do to fix it.

Any ideas?

Thanks,
-- Scott


-------------- [1] --------------


[java] !ENTRY org.eclipse.buckminster.core 4 293 2009-08-05
09:06:09.085
[java] !MESSAGE org.eclipse.core.runtime.CoreException:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
The following error occurred while executing this line:
[java]
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
doesn't exist
[java] !STACK 1
[java] org.eclipse.core.runtime.CoreException:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
The following error occurred while executing this line:
[java]
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
doesn't exist
[java] at
org.eclipse.buckminster.ant.AntRunner.handleInvocationTarget Exception(AntRunner.java:189)
[java] at
org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:352 )
[java] at
org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:281)
[java] at
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
[java] at
org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:118)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
[java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
[java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
[java] Caused by:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
The following error occurred while executing this line:
[java]
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
doesn't exist
[java] at
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:508)
[java] at
org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:397)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
[java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
[java] at org.apache.tools.ant.Task.perform(Task.java:348)
[java] at org.apache.tools.ant.Target.execute(Target.java:357)
[java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[java] at
org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1337)
[java] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306 )
[java] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
[java] at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
[java] at
org.apache.tools.ant.Project.executeTargets(Project.java:118 9)
[java] at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:622)
[java] at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:455)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:344 )
[java] ... 23 more
[java] Caused by:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
doesn't exist
[java] at
org.apache.tools.ant.taskdefs.LoadResource.execute(LoadResou rce.java:142)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
[java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
[java] at org.apache.tools.ant.Task.perform(Task.java:348)
[java] at
org.apache.tools.ant.taskdefs.Sequential.execute(Sequential. java:62)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
[java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
[java] at org.apache.tools.ant.Task.perform(Task.java:348)
[java] at
org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:394)
[java] ... 43 more


-------------- [2] --------------


[java] org.eclipse.buckminster.pde.targetPlatformPath
[java] Description: Set the active Target Platform to a definition
that appoints a path
[java] org.eclipse.core.runtime.CoreException: Active target 'Eclipse
SDK with delta pack' is too complex to be represented by a single path
[java] at
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:64)
[java] at
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:59)
[java] at
org.eclipse.buckminster.pde.prefs.TargetPlatformPathHandler. get(TargetPlatformPathHandler.java:51)
[java] at
org.eclipse.buckminster.core.commands.ListPreferences.run(Li stPreferences.java:93)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
[java] at
org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
[java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
[java] Active target 'Eclipse SDK with delta pack' is too complex to
be represented by a single path






Thomas Hallgren wrote:

> Hi Scott,
> You don't have any installLocation set for your p2 materializer so you
probably hit what's described here:

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285449

> You can try the following:
> 1. Create an empty folder that will be the destination for the things you
want to materialize into your TP.
> 2. Add this folder as a "Directory" to your active TP.

> That should do the trick.

> HTH,
> Thomas Hallgren


> Scott Hendrickson wrote:
>> Any suggestions? Is anyone else able to successfully perform this build
>> (note: this is very small. It checks out a feature, which includes a
>> single prodjct, which depends on org.eclipse.emf). I'll include the
>> relevant files, below, in case that helps anyone in figuring out what's
>> going on.
>>
>> I made the ant build script so that it would be easy for someone else to
>> see what I'm doing and reproduce the error. I hope it helps!
>>
>> Thank you,
>> -- Scott
>>
>> ------------------------------ Target Platform:
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> <?pde version="3.5"?>
>>
>> <target name="Eclipse SDK with delta pack">
>> <locations>
>> <location includeAllPlatforms="true" includeMode="slicer"
>> type="InstallableUnit">
>> <unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
>> <repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
>> </location>
>> </locations>
>> </target>
>>
>> ------------------------------ MSPEC:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
>> name="workspace materializer by default, P2 otherwise"
>> shortDesc="update_site_workspace_p2"
>> materializer="workspace"
>> conflictResolution="UPDATE"
>> url="./update_site.cquery" >
>> <md:property key="eclipse.version" value="3.4"/>
>> <md:mspecNode namePattern="^org.eclipse(.[^.]+)*$"
>> materializer="p2" conflictResolution="UPDATE" />
>> </md:mspec>
>>
>> ------------------------------ CQUERY:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <cq:componentQuery
>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>
resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
>>
>> <cq:rootRequest
>> name="edu.uci.isr.infrastructure.update_site_with_feature"
>> componentType="buckminster"/>
>> <cq:property key="eclipse.version" value="3.4"/>
>> <cq:advisorNode namePattern="^edu.uci.isr..*$"
>> useTargetPlatform="false" branchTagPath="main"/>
>> </cq:componentQuery>
>>
>> ------------------------------ Result from build:
>>
>> "Error: file
>>
C:Usersscotteclipseworkspacesbuck-testedu.uci.isr.infrastruc ture.buckminster_build_testtempbuckminsterworkspacepluginsed u.uci.isr.infrastructure.project_requiring_emfMETA-INFMANIFE ST.MF,
>> line 7: Bundle 'org.eclipse.emf' cannot be resolved"
>>
>> ------------------------------ Result from running the action (and
>> skipping the build):
>>
>> ${sp:manifest} is undefined
>>
>>
>>
Re: Build fails after headless resolve using p2 [message #478257 is a reply to message #470843] Thu, 06 August 2009 09:03 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Scott,
The second problem looks as a bug. Can you please enter a bugzilla on that so we don't loose track of it?

I'm on vacation now (back on Monday) so some things are moving slower then others. I'll take a look problem #1 when I
get back.

Regards,
Thomas Hallgren

Scott Hendrickson wrote:
> Hi Thomas,
>
> Thanks for your response. I've done as you suggested and the
> org.eclipse.emf plugin is now placed in a "target" folder that I've
> added to the target platform definition. However, when I still get the
> following error:
>
> 1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
> doesn't exist (details below: [1])
>
> NOTE: I updated the build script to insert the local path manually for
> the location using an xstl.
>
> I also noticed that when I execute a lsprefs command, I now get the
> following exception:
>
> 2) "Active target 'Eclipse SDK with delta pack' is too complex to be
> represented by a single path" (details below: [2]). This should probably
> report the issue, but not throw an exception - halting the process.
>
> The second issue is not a show stopper, I just commented out these
> commands. But, I'm not sure what to do to fix the fist issue.
>
> The update site's buckminster.cspec was created using the instructions
> here:
> http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster
> So, I think I have everything in there (and this used to work), but I'm
> not sure what I need to do to fix it.
>
> Any ideas?
>
> Thanks,
> -- Scott
>
>
> -------------- [1] --------------
>
> [java] !ENTRY org.eclipse.buckminster.core 4 293 2009-08-05
> 09:06:09.085
> [java] !MESSAGE org.eclipse.core.runtime.CoreException:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
> The following error occurred while executing this line:
> [java]
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
> doesn't exist
> [java] !STACK 1
> [java] org.eclipse.core.runtime.CoreException:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
> The following error occurred while executing this line:
> [java]
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
> doesn't exist
> [java] at
> org.eclipse.buckminster.ant.AntRunner.handleInvocationTarget Exception(AntRunner.java:189)
>
> [java] at
> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:352 )
> [java] at
> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:281)
>
> [java] at
> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
>
> [java] at
> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:118)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
>
> [java] at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
> [java] at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
> [java] Caused by:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
> The following error occurred while executing this line:
> [java]
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
> doesn't exist
> [java] at
> org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:508)
>
> [java] at
> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:397)
> [java] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
> Source)
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:357)
> [java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
> [java] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1337)
> [java] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1306 )
> [java] at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>
> [java] at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> [java] at
> org.apache.tools.ant.Project.executeTargets(Project.java:118 9)
> [java] at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:622)
>
> [java] at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:455)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:344 )
> [java] ... 23 more
> [java] Caused by:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
> /home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
> doesn't exist
> [java] at
> org.apache.tools.ant.taskdefs.LoadResource.execute(LoadResou rce.java:142)
> [java] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
> Source)
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at
> org.apache.tools.ant.taskdefs.Sequential.execute(Sequential. java:62)
> [java] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
> Source)
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at
> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:394)
> [java] ... 43 more
>
>
> -------------- [2] --------------
>
>
> [java] org.eclipse.buckminster.pde.targetPlatformPath
> [java] Description: Set the active Target Platform to a definition
> that appoints a path
> [java] org.eclipse.core.runtime.CoreException: Active target
> 'Eclipse SDK with delta pack' is too complex to be represented by a
> single path
> [java] at
> org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:64)
>
> [java] at
> org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:59)
>
> [java] at
> org.eclipse.buckminster.pde.prefs.TargetPlatformPathHandler. get(TargetPlatformPathHandler.java:51)
>
> [java] at
> org.eclipse.buckminster.core.commands.ListPreferences.run(Li stPreferences.java:93)
>
> [java] at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
> [java] at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
> [java] Active target 'Eclipse SDK with delta pack' is too complex to
> be represented by a single path
>
>
>
>
>
>
> Thomas Hallgren wrote:
>
>> Hi Scott,
>> You don't have any installLocation set for your p2 materializer so you
> probably hit what's described here:
>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285449
>
>> You can try the following:
>> 1. Create an empty folder that will be the destination for the things you
> want to materialize into your TP.
>> 2. Add this folder as a "Directory" to your active TP.
>
>> That should do the trick.
>
>> HTH,
>> Thomas Hallgren
>
>
>> Scott Hendrickson wrote:
>>> Any suggestions? Is anyone else able to successfully perform this
>>> build (note: this is very small. It checks out a feature, which
>>> includes a single prodjct, which depends on org.eclipse.emf). I'll
>>> include the relevant files, below, in case that helps anyone in
>>> figuring out what's going on.
>>>
>>> I made the ant build script so that it would be easy for someone else
>>> to see what I'm doing and reproduce the error. I hope it helps!
>>>
>>> Thank you,
>>> -- Scott
>>>
>>> ------------------------------ Target Platform:
>>>
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <?pde version="3.5"?>
>>>
>>> <target name="Eclipse SDK with delta pack">
>>> <locations>
>>> <location includeAllPlatforms="true" includeMode="slicer"
>>> type="InstallableUnit">
>>> <unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
>>> <repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
>>> </location>
>>> </locations>
>>> </target>
>>>
>>> ------------------------------ MSPEC:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
>>> name="workspace materializer by default, P2 otherwise"
>>> shortDesc="update_site_workspace_p2"
>>> materializer="workspace"
>>> conflictResolution="UPDATE"
>>> url="./update_site.cquery" >
>>> <md:property key="eclipse.version" value="3.4"/>
>>> <md:mspecNode namePattern="^org.eclipse(.[^.]+)*$"
>>> materializer="p2" conflictResolution="UPDATE" />
>>> </md:mspec>
>>>
>>> ------------------------------ CQUERY:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <cq:componentQuery
>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
> resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
>
>>>
>>> <cq:rootRequest
>>> name="edu.uci.isr.infrastructure.update_site_with_feature"
>>> componentType="buckminster"/>
>>> <cq:property key="eclipse.version" value="3.4"/>
>>> <cq:advisorNode namePattern="^edu.uci.isr..*$"
>>> useTargetPlatform="false" branchTagPath="main"/>
>>> </cq:componentQuery>
>>>
>>> ------------------------------ Result from build:
>>>
>>> "Error: file
> C:Usersscotteclipseworkspacesbuck-testedu.uci.isr.infrastruc ture.buckminster_build_testtempbuckminsterworkspacepluginsed u.uci.isr.infrastructure.project_requiring_emfMETA-INFMANIFE ST.MF,
>
>>> line 7: Bundle 'org.eclipse.emf' cannot be resolved"
>>>
>>> ------------------------------ Result from running the action (and
>>> skipping the build):
>>>
>>> ${sp:manifest} is undefined
>>>
>>>
>>>
>
Re: Build fails after headless resolve using p2 [message #480600 is a reply to message #478257] Mon, 17 August 2009 19:45 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Thomas Hallgren wrote:

> Hi Scott,
> The second problem looks as a bug. Can you please enter a bugzilla on that
so we don't loose track of it?

Done:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=286860

Let me know if you need any help reproducing the first issue.

Thank you,
-- Scott

> I'm on vacation now (back on Monday) so some things are moving slower then
others. I'll take a look problem #1 when I
> get back.

> Regards,
> Thomas Hallgren

> Scott Hendrickson wrote:
>> Hi Thomas,
>>
>> Thanks for your response. I've done as you suggested and the
>> org.eclipse.emf plugin is now placed in a "target" folder that I've
>> added to the target platform definition. However, when I still get the
>> following error:
>>
>> 1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>> doesn't exist (details below: [1])
>>
>> NOTE: I updated the build script to insert the local path manually for
>> the location using an xstl.
>>
>> I also noticed that when I execute a lsprefs command, I now get the
>> following exception:
>>
>> 2) "Active target 'Eclipse SDK with delta pack' is too complex to be
>> represented by a single path" (details below: [2]). This should probably
>> report the issue, but not throw an exception - halting the process.
>>
>> The second issue is not a show stopper, I just commented out these
>> commands. But, I'm not sure what to do to fix the fist issue.
>>
>> The update site's buckminster.cspec was created using the instructions
>> here:
>> http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster
>> So, I think I have everything in there (and this used to work), but I'm
>> not sure what I need to do to fix it.
>>
>> Any ideas?
>>
>> Thanks,
>> -- Scott
>>
>>
>> -------------- [1] --------------
>>
>> [java] !ENTRY org.eclipse.buckminster.core 4 293 2009-08-05
>> 09:06:09.085
>> [java] !MESSAGE org.eclipse.core.runtime.CoreException:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>> The following error occurred while executing this line:
>> [java]
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>> doesn't exist
>> [java] !STACK 1
>> [java] org.eclipse.core.runtime.CoreException:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>> The following error occurred while executing this line:
>> [java]
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>> doesn't exist
>> [java] at
>>
org.eclipse.buckminster.ant.AntRunner.handleInvocationTarget Exception(AntRunner.java:189)
>>
>> [java] at
>> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:352 )
>> [java] at
>>
org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:281)
>>
>> [java] at
>>
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
>>
>> [java] at
>>
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
>>
>> [java] at
>>
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
>>
>> [java] at
>> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:118)
>> [java] at
>>
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
>>
>> [java] at
>>
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>>
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
>> [java] at
>>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>>
>> [java] at
>>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>
>> [java] at
>>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>
>> [java] at
>>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>
>> [java] at
>>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>> [java] Caused by:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>> The following error occurred while executing this line:
>> [java]
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>> doesn't exist
>> [java] at
>>
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:508)
>>
>> [java] at
>> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:397)
>> [java] at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>> Source)
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>> [java] at org.apache.tools.ant.Target.execute(Target.java:357)
>> [java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> [java] at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1337)
>> [java] at
>> org.apache.tools.ant.Project.executeTarget(Project.java:1306 )
>> [java] at
>>
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>>
>> [java] at
>>
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>
>> [java] at
>> org.apache.tools.ant.Project.executeTargets(Project.java:118 9)
>> [java] at
>>
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:622)
>>
>> [java] at
>>
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:455)
>>
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:344 )
>> [java] ... 23 more
>> [java] Caused by:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>> doesn't exist
>> [java] at
>> org.apache.tools.ant.taskdefs.LoadResource.execute(LoadResou rce.java:142)
>> [java] at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>> Source)
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>> [java] at
>> org.apache.tools.ant.taskdefs.Sequential.execute(Sequential. java:62)
>> [java] at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>> Source)
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>> [java] at
>> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:394)
>> [java] ... 43 more
>>
>>
>> -------------- [2] --------------
>>
>>
>> [java] org.eclipse.buckminster.pde.targetPlatformPath
>> [java] Description: Set the active Target Platform to a definition
>> that appoints a path
>> [java] org.eclipse.core.runtime.CoreException: Active target
>> 'Eclipse SDK with delta pack' is too complex to be represented by a
>> single path
>> [java] at
>>
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:64)
>>
>> [java] at
>>
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:59)
>>
>> [java] at
>>
org.eclipse.buckminster.pde.prefs.TargetPlatformPathHandler. get(TargetPlatformPathHandler.java:51)
>>
>> [java] at
>>
org.eclipse.buckminster.core.commands.ListPreferences.run(Li stPreferences.java:93)
>>
>> [java] at
>>
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>>
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
>> [java] at
>>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>>
>> [java] at
>>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>
>> [java] at
>>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>
>> [java] at
>>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>
>> [java] at
>>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>> [java] at
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>> [java] Active target 'Eclipse SDK with delta pack' is too complex to
>> be represented by a single path
>>
>>
>>
>>
>>
>>
>> Thomas Hallgren wrote:
>>
>>> Hi Scott,
>>> You don't have any installLocation set for your p2 materializer so you
>> probably hit what's described here:
>>
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285449
>>
>>> You can try the following:
>>> 1. Create an empty folder that will be the destination for the things you
>> want to materialize into your TP.
>>> 2. Add this folder as a "Directory" to your active TP.
>>
>>> That should do the trick.
>>
>>> HTH,
>>> Thomas Hallgren
>>
>>
>>> Scott Hendrickson wrote:
>>>> Any suggestions? Is anyone else able to successfully perform this
>>>> build (note: this is very small. It checks out a feature, which
>>>> includes a single prodjct, which depends on org.eclipse.emf). I'll
>>>> include the relevant files, below, in case that helps anyone in
>>>> figuring out what's going on.
>>>>
>>>> I made the ant build script so that it would be easy for someone else
>>>> to see what I'm doing and reproduce the error. I hope it helps!
>>>>
>>>> Thank you,
>>>> -- Scott
>>>>
>>>> ------------------------------ Target Platform:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>>> <?pde version="3.5"?>
>>>>
>>>> <target name="Eclipse SDK with delta pack">
>>>> <locations>
>>>> <location includeAllPlatforms="true" includeMode="slicer"
>>>> type="InstallableUnit">
>>>> <unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
>>>> <repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
>>>> </location>
>>>> </locations>
>>>> </target>
>>>>
>>>> ------------------------------ MSPEC:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
>>>> name="workspace materializer by default, P2 otherwise"
>>>> shortDesc="update_site_workspace_p2"
>>>> materializer="workspace"
>>>> conflictResolution="UPDATE"
>>>> url="./update_site.cquery" >
>>>> <md:property key="eclipse.version" value="3.4"/>
>>>> <md:mspecNode namePattern="^org.eclipse(.[^.]+)*$"
>>>> materializer="p2" conflictResolution="UPDATE" />
>>>> </md:mspec>
>>>>
>>>> ------------------------------ CQUERY:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <cq:componentQuery
>>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>
resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
>>
>>>>
>>>> <cq:rootRequest
>>>> name="edu.uci.isr.infrastructure.update_site_with_feature"
>>>> componentType="buckminster"/>
>>>> <cq:property key="eclipse.version" value="3.4"/>
>>>> <cq:advisorNode namePattern="^edu.uci.isr..*$"
>>>> useTargetPlatform="false" branchTagPath="main"/>
>>>> </cq:componentQuery>
>>>>
>>>> ------------------------------ Result from build:
>>>>
>>>> "Error: file
>>
C:Usersscotteclipseworkspacesbuck-testedu.uci.isr.infrastruc ture.buckminster_build_testtempbuckminsterworkspacepluginsed u.uci.isr.infrastructure.project_requiring_emfMETA-INFMANIFE ST.MF,
>>
>>>> line 7: Bundle 'org.eclipse.emf' cannot be resolved"
>>>>
>>>> ------------------------------ Result from running the action (and
>>>> skipping the build):
>>>>
>>>> ${sp:manifest} is undefined
>>>>
>>>>
>>>>
>>
Re: Build fails after headless resolve using p2 [message #481147 is a reply to message #480600] Wed, 19 August 2009 18:20 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Scott Hendrickson wrote:

Thanks Thomas for fixing the second issue. Any ideas on the first?

>>> 1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>>> doesn't exist (details below: [1])
>>>
>>> NOTE: I updated the build script to insert the local path manually for
>>> the location using an xstl.

The build script is here:

http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu .uci.isr.infrastructure.buckminster_build_test/build.xml

-- Scott


> Thomas Hallgren wrote:

>> Hi Scott,
>> The second problem looks as a bug. Can you please enter a bugzilla on that
> so we don't loose track of it?

> Done:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=286860

> Let me know if you need any help reproducing the first issue.

> Thank you,
> -- Scott

>> I'm on vacation now (back on Monday) so some things are moving slower then
> others. I'll take a look problem #1 when I
>> get back.

>> Regards,
>> Thomas Hallgren

>> Scott Hendrickson wrote:
>>> Hi Thomas,
>>>
>>> Thanks for your response. I've done as you suggested and the
>>> org.eclipse.emf plugin is now placed in a "target" folder that I've
>>> added to the target platform definition. However, when I still get the
>>> following error:
>>>
>>> 1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>>> doesn't exist (details below: [1])
>>>
>>> NOTE: I updated the build script to insert the local path manually for
>>> the location using an xstl.
>>>
>>> I also noticed that when I execute a lsprefs command, I now get the
>>> following exception:
>>>
>>> 2) "Active target 'Eclipse SDK with delta pack' is too complex to be
>>> represented by a single path" (details below: [2]). This should probably
>>> report the issue, but not throw an exception - halting the process.
>>>
>>> The second issue is not a show stopper, I just commented out these
>>> commands. But, I'm not sure what to do to fix the fist issue.
>>>
>>> The update site's buckminster.cspec was created using the instructions
>>> here:
>>> http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster
>>> So, I think I have everything in there (and this used to work), but I'm
>>> not sure what I need to do to fix it.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> -- Scott
>>>
>>>
>>> -------------- [1] --------------
>>>
>>> [java] !ENTRY org.eclipse.buckminster.core 4 293 2009-08-05
>>> 09:06:09.085
>>> [java] !MESSAGE org.eclipse.core.runtime.CoreException:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>>> The following error occurred while executing this line:
>>> [java]
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>>> doesn't exist
>>> [java] !STACK 1
>>> [java] org.eclipse.core.runtime.CoreException:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>>> The following error occurred while executing this line:
>>> [java]
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>>> doesn't exist
>>> [java] at
>>>
>
org.eclipse.buckminster.ant.AntRunner.handleInvocationTarget Exception(AntRunner.java:189)
>>>
>>> [java] at
>>> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:352 )
>>> [java] at
>>>
>
org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:281)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
>>>
>>> [java] at
>>> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:118)
>>> [java] at
>>>
>
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>>>
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
>>> [java] at
>>>
>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>>>
>>> [java] at
>>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>>
>>> [java] at
>>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>>
>>> [java] at
>>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>>
>>> [java] at
>>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>>
>>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> [java] at
>>>
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>>> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>>> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>>> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>>> [java] Caused by:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:117:
>>> The following error occurred while executing this line:
>>> [java]
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>>> doesn't exist
>>> [java] at
>>>
>
org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti on(ProjectHelper.java:508)
>>>
>>> [java] at
>>> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:397)
>>> [java] at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>>> Source)
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>>> [java] at org.apache.tools.ant.Target.execute(Target.java:357)
>>> [java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
>>> [java] at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1337)
>>> [java] at
>>> org.apache.tools.ant.Project.executeTarget(Project.java:1306 )
>>> [java] at
>>>
>
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>>>
>>> [java] at
>>>
>
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>>
>>> [java] at
>>> org.apache.tools.ant.Project.executeTargets(Project.java:118 9)
>>> [java] at
>>>
>
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:622)
>>>
>>> [java] at
>>>
>
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:455)
>>>
>>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> [java] at
>>>
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:344 )
>>> [java] ... 23 more
>>> [java] Caused by:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/configuration/org.eclipse.osgi/bundles/80/1/.cp/ org/eclipse/buckminster/pde/antscripts/build.xml:53:
>>>
>
/home/scott/infrastructure/bitten/slaves/java1.5-eclipse3.4/ buckminster/workspace/edu.uci.isr.infrastructure.update_site _with_feature/${sp:manifest}
>>> doesn't exist
>>> [java] at
>>> org.apache.tools.ant.taskdefs.LoadResource.execute(LoadResou rce.java:142)
>>> [java] at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>>> Source)
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>>> [java] at
>>> org.apache.tools.ant.taskdefs.Sequential.execute(Sequential. java:62)
>>> [java] at
>>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>>> [java] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
>>> Source)
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
>>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>>> [java] at
>>> org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns tance.java:394)
>>> [java] ... 43 more
>>>
>>>
>>> -------------- [2] --------------
>>>
>>>
>>> [java] org.eclipse.buckminster.pde.targetPlatformPath
>>> [java] Description: Set the active Target Platform to a definition
>>> that appoints a path
>>> [java] org.eclipse.core.runtime.CoreException: Active target
>>> 'Eclipse SDK with delta pack' is too complex to be represented by a
>>> single path
>>> [java] at
>>>
>
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:64)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.runtime.BuckminsterException.fromMes sage(BuckminsterException.java:59)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.pde.prefs.TargetPlatformPathHandler. get(TargetPlatformPathHandler.java:51)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.core.commands.ListPreferences.run(Li stPreferences.java:93)
>>>
>>> [java] at
>>>
>
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>>>
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
>>> [java] at
>>> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
>>> [java] at
>>>
>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
>>>
>>> [java] at
>>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>>
>>> [java] at
>>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>>
>>> [java] at
>>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
>>>
>>> [java] at
>>>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>>
>>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> [java] at
>>>
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> [java] at
>>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> [java] at java.lang.reflect.Method.invoke(Method.java:585)
>>> [java] at
>>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>>> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>>> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>>> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>>> [java] Active target 'Eclipse SDK with delta pack' is too complex to
>>> be represented by a single path
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thomas Hallgren wrote:
>>>
>>>> Hi Scott,
>>>> You don't have any installLocation set for your p2 materializer so you
>>> probably hit what's described here:
>>>
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285449
>>>
>>>> You can try the following:
>>>> 1. Create an empty folder that will be the destination for the things you
>>> want to materialize into your TP.
>>>> 2. Add this folder as a "Directory" to your active TP.
>>>
>>>> That should do the trick.
>>>
>>>> HTH,
>>>> Thomas Hallgren
>>>
>>>
>>>> Scott Hendrickson wrote:
>>>>> Any suggestions? Is anyone else able to successfully perform this
>>>>> build (note: this is very small. It checks out a feature, which
>>>>> includes a single prodjct, which depends on org.eclipse.emf). I'll
>>>>> include the relevant files, below, in case that helps anyone in
>>>>> figuring out what's going on.
>>>>>
>>>>> I made the ant build script so that it would be easy for someone else
>>>>> to see what I'm doing and reproduce the error. I hope it helps!
>>>>>
>>>>> Thank you,
>>>>> -- Scott
>>>>>
>>>>> ------------------------------ Target Platform:
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>>>> <?pde version="3.5"?>
>>>>>
>>>>> <target name="Eclipse SDK with delta pack">
>>>>> <locations>
>>>>> <location includeAllPlatforms="true" includeMode="slicer"
>>>>> type="InstallableUnit">
>>>>> <unit id="org.eclipse.sdk.ide" version="3.4.2.M20090211-1700"/>
>>>>> <repository location="http://download.eclipse.org/eclipse/updates/3.4"/>
>>>>> </location>
>>>>> </locations>
>>>>> </target>
>>>>>
>>>>> ------------------------------ MSPEC:
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
>>>>> name="workspace materializer by default, P2 otherwise"
>>>>> shortDesc="update_site_workspace_p2"
>>>>> materializer="workspace"
>>>>> conflictResolution="UPDATE"
>>>>> url="./update_site.cquery" >
>>>>> <md:property key="eclipse.version" value="3.4"/>
>>>>> <md:mspecNode namePattern="^org.eclipse(.[^.]+)*$"
>>>>> materializer="p2" conflictResolution="UPDATE" />
>>>>> </md:mspec>
>>>>>
>>>>> ------------------------------ CQUERY:
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <cq:componentQuery
>>>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>>
>
resourceMap=" http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/inf rastructure/tps.ics.uci.edu.rmap">
>>>
>>>>>
>>>>> <cq:rootRequest
>>>>> name="edu.uci.isr.infrastructure.update_site_with_feature"
>>>>> componentType="buckminster"/>
>>>>> <cq:property key="eclipse.version" value="3.4"/>
>>>>> <cq:advisorNode namePattern="^edu.uci.isr..*$"
>>>>> useTargetPlatform="false" branchTagPath="main"/>
>>>>> </cq:componentQuery>
>>>>>
>>>>> ------------------------------ Result from build:
>>>>>
>>>>> "Error: file
>>>
>
C:Usersscotteclipseworkspacesbuck-testedu.uci.isr.infrastruc ture.buckminster_build_testtempbuckminsterworkspacepluginsed u.uci.isr.infrastructure.project_requiring_emfMETA-INFMANIFE ST.MF,
>>>
>>>>> line 7: Bundle 'org.eclipse.emf' cannot be resolved"
>>>>>
>>>>> ------------------------------ Result from running the action (and
>>>>> skipping the build):
>>>>>
>>>>> ${sp:manifest} is undefined
>>>>>
>>>>>
>>>>>
>>>
Re: Build fails after headless resolve using p2 [message #481159 is a reply to message #481147] Wed, 19 August 2009 20:42 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Scott,
I looked at your build. Apparently you have handcrafted a cspec that calls the create.site task in the
buckminster.pdetasks script. That particular task did undergo significant changes when we moved to p2 which begs the
question, what type of update site is it that you want to create? A legacy update site or a p2 repository? If it's the
latter, then you can simplify the creation of that update site a great deal by using the "Update sites using the 3.5
release" section rather then the "Update sites using the 3.4.x and earlier releases" on the
http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster page.

Regards,
Thomas Hallgren


On 08/19/2009 08:20 PM, Scott Hendrickson wrote:
> Scott Hendrickson wrote:
>
> Thanks Thomas for fixing the second issue. Any ideas on the first?
>
>>>> 1)
>>>> edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>>>> doesn't exist (details below: [1])
>>>>
>>>> NOTE: I updated the build script to insert the local path manually
>>>> for the location using an xstl.
>
> The build script is here:
>
> http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu .uci.isr.infrastructure.buckminster_build_test/build.xml
>
>
> -- Scott
Re: Build fails after headless resolve using p2 [message #481182 is a reply to message #481159] Thu, 20 August 2009 02:01 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Hi Thomas,

Unfortunately, I am wanting to create a legacy update site. The cspec is
what results from directly following the instructions for the "Update
sites using the 3.4.x and earlier releases" on the page that you mentioned
(without any of the optional features like groups; but, the error occurs
when groups are present as well).

If you follow the instructions on the page to create a legacy update site,
you'll run in to the same error.

-- Scott


Thomas Hallgren wrote:

> Hi Scott,
> I looked at your build. Apparently you have handcrafted a cspec that calls
the create.site task in the
> buckminster.pdetasks script. That particular task did undergo significant
changes when we moved to p2 which begs the
> question, what type of update site is it that you want to create? A legacy
update site or a p2 repository? If it's the
> latter, then you can simplify the creation of that update site a great deal
by using the "Update sites using the 3.5
> release" section rather then the "Update sites using the 3.4.x and earlier
releases" on the
> http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster page.

> Regards,
> Thomas Hallgren


> On 08/19/2009 08:20 PM, Scott Hendrickson wrote:
>> Scott Hendrickson wrote:
>>
>> Thanks Thomas for fixing the second issue. Any ideas on the first?
>>
>>>>> 1)
>>>>> edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>>>>> doesn't exist (details below: [1])
>>>>>
>>>>> NOTE: I updated the build script to insert the local path manually
>>>>> for the location using an xstl.
>>
>> The build script is here:
>>
>>
http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu .uci.isr.infrastructure.buckminster_build_test/build.xml
>>
>>
>> -- Scott
Re: Build fails after headless resolve using p2 [message #481183 is a reply to message #481182] Thu, 20 August 2009 02:37 Go to previous messageGo to next message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
Scott Hendrickson wrote:

> Hi Thomas,

> Unfortunately, I am wanting to create a legacy update site. The cspec is
> what results from directly following the instructions for the "Update
> sites using the 3.4.x and earlier releases" on the page that you mentioned
> (without any of the optional features like groups; but, the error occurs
> when groups are present as well).

Oh, there is one modification. The "build.site" action in the cspec is
what you get when you follow the instructions. It calls the "create.site"
task. However, in (headless) buckminster 3.5, there is no "create.site"
task. So, I created a duplicate called "build.site.5", which calls the
"create.site.zip" task, which does exist in headless buckminster 3.5 (and
3.4 as well, iirc).

This all started with this message:
http://dev.eclipse.org/newslists/news.eclipse.tools.buckmins ter/msg01114.html
(I accidentally replied only to you and not the newsgroup that I was using
3.4, and you suggested trying out 3.5). Since then, as I've had time, I've
been transitioning to the headless buckminster 3.5. But, it seems to be
broken with respect to building legacy update sites.

I hope that helps :)

Thanks,
-- Scott


> If you follow the instructions on the page to create a legacy update site,
> you'll run in to the same error.

> -- Scott


> Thomas Hallgren wrote:

>> Hi Scott,
>> I looked at your build. Apparently you have handcrafted a cspec that calls
> the create.site task in the
>> buckminster.pdetasks script. That particular task did undergo significant
> changes when we moved to p2 which begs the
>> question, what type of update site is it that you want to create? A legacy
> update site or a p2 repository? If it's the
>> latter, then you can simplify the creation of that update site a great deal
> by using the "Update sites using the 3.5
>> release" section rather then the "Update sites using the 3.4.x and earlier
> releases" on the
>> http://wiki.eclipse.org/Building_an_Update_Site_using_Buckmi nster page.

>> Regards,
>> Thomas Hallgren


>> On 08/19/2009 08:20 PM, Scott Hendrickson wrote:
>>> Scott Hendrickson wrote:
>>>
>>> Thanks Thomas for fixing the second issue. Any ideas on the first?
>>>
>>>>>> 1)
>>>>>> edu.uci.isr.infrastructure.update_site_with_feature/${sp:man ifest}
>>>>>> doesn't exist (details below: [1])
>>>>>>
>>>>>> NOTE: I updated the build script to insert the local path manually
>>>>>> for the location using an xstl.
>>>
>>> The build script is here:
>>>
>>>
>
http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu .uci.isr.infrastructure.buckminster_build_test/build.xml
>>>
>>>
>>> -- Scott
Re: Build fails after headless resolve using p2 [message #481243 is a reply to message #481183] Thu, 20 August 2009 08:43 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Scott,
We dropped the support for building legacy update sites in our Galileo release. The rationale for this was that legacy
sites were no longer provided with Galileo and even with Ganymede, P2 was available. Only users on 3.3 or older are
confined to use legacy update sites and our Ganymede release was still there if you wanted to do that.

I can see how that was a bad decision. P2 wasn't very mature in Ganymede so a lot of users still use the legacy UM. We
don't want to force users like yourself to use our old Ganymede release to accommodate that. I therefore reinstated the
support for legacy update sites. The task names are slightly different ('create.legacy.site' instead of 'create.site'). See:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=287146

I tested your build.xml and it seems to run just fine after changing the task names.

I'm uploading updated bundles to our update sites right now. They will be available in an hour or so.

Regards,
Thomas Hallgren
Re: Build fails after headless resolve using p2 [message #481385 is a reply to message #481243] Thu, 20 August 2009 17:29 Go to previous message
Scott Hendrickson is currently offline Scott HendricksonFriend
Messages: 69
Registered: July 2009
Member
This is great. Thank you Thomas for hanging in there while I tried to
articulate what the problem was and for getting a fix in :) The result is
perfectly suitable for me.
-- Scott

Thomas Hallgren wrote:

> Hi Scott,
> We dropped the support for building legacy update sites in our Galileo
release. The rationale for this was that legacy
> sites were no longer provided with Galileo and even with Ganymede, P2 was
available. Only users on 3.3 or older are
> confined to use legacy update sites and our Ganymede release was still there
if you wanted to do that.

> I can see how that was a bad decision. P2 wasn't very mature in Ganymede so
a lot of users still use the legacy UM. We
> don't want to force users like yourself to use our old Ganymede release to
accommodate that. I therefore reinstated the
> support for legacy update sites. The task names are slightly different
('create.legacy.site' instead of 'create.site'). See:

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=287146

> I tested your build.xml and it seems to run just fine after changing the
task names.

> I'm uploading updated bundles to our update sites right now. They will be
available in an hour or so.

> Regards,
> Thomas Hallgren
Previous Topic:How to include component version with an action path
Next Topic:Hudson Plugin for Buckminster
Goto Forum:
  


Current Time: Wed Apr 24 18:57:44 GMT 2024

Powered by FUDForum. Page generated in 0.03811 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top