| Issue with Buckminster build after upgrade to Eclipse RC1 Platform [message #385462] |
Mon, 18 May 2009 22:11  |
 Oisin Hurley
Messages: 204
Registered: July 2009 |
Senior Member |
|
|
It wouldn't be a milestone release date without some kind of issue
coming up :(
I'm just wondering if anyone else who is building might have seen
this.
When performing an STP build against 3.5M7, everything runs
swimmingly, but when I perform the same build against the
3.5RC1 release of the Eclipse platform, I get a failure for one
of the components:
[java] org.eclipse.core.runtime.CoreException: The project cannot be
built until its prerequisite com.ibm.icu is built. Cleaning and building
all projects is recommended
[java] at
org.eclipse.buckminster.core.internal.actor.AbstractBuildInt egrationActor.internalPerform(AbstractBuildIntegrationActor. java:53)
[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:198)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
[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:79)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
[java] at java.lang.reflect.Method.invoke(Method.java:618)
[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] The project cannot be built until its prerequisite com.ibm.icu
is built. Cleaning and building all projects is recommended
Previously, everything has resolved correctly, so all of the plugins that
are needed are in place as far as Buckminster is concerned.
I took the offending project out of the build, and carried on, but in
then another project would fail in a similar fashion. I eventually brought
the build down to a single sub-project, but that also failed in the same
manner, but citing a different plugin (org.jdom) as the one that needed
to be built.
The only common behaviour I see is that each time the 'cannot be built'
issue refers to a prerequisite that is part of Orbit, which is read using
eclipse.import from a remote map file:
<provider readerType="eclipse.import" componentTypes="osgi.bundle"
mutable="false" source="false">
<uri
format=" http://download.eclipse.org/tools/orbit/downloads/drops/I200 90504052954/orbitBundles-I20090504052954.map"
/>
</provider>
the map file exists and is valid (and has been used for M7).
To take the remote issue out of the picture, I downloaded Orbit as a
whole and unzipped it locally, then used a provider with a file: URI:
<provider readerType="eclipse.import" componentTypes="osgi.bundle"
mutable="false" source="false">
<uri format="{0}/orbit/eclipse">
<bc:propertyRef key="project.root" />
</uri>
</provider>
The required orbit plugins are materialized from the local file system
into the local workspace as expected, however the "project cannot be
built" happens at the end of the build.
Easiest way to reproduce this is to do a build on the build.eclipse.org
infrastructure. Check out the STP Policy sub-project build:
svn co
http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.policy-ed itor/org.eclipse.stp.policy/trunk/build
cd build/policy
Then run a successful build with:
ant -Dbase.directory=`pwd`/m7
-Dplatform=/shared/stp/platforms/3.5M7/eclipse build
and then run a failed build with
ant -Dbase.directory=`pwd`/mrc1
-Dplatform=/shared/stp/platforms/3.5RC1/eclipse build
The only thing that has changed is the platform - so I have to suspect
that
first and foremost. What could have changed here?
--oh
|
|
|
| Re: Issue with Buckminster build after upgrade to Eclipse RC1 Platform [message #385465 is a reply to message #385462] |
Tue, 19 May 2009 07:12  |
|
Hi Oisin,
I'll try to reproduce this locally. It's hard to do meaningful debugging on the build machine.
- thomas
Oisin Hurley wrote:
> It wouldn't be a milestone release date without some kind of issue
> coming up :(
>
> I'm just wondering if anyone else who is building might have seen
> this.
>
> When performing an STP build against 3.5M7, everything runs swimmingly,
> but when I perform the same build against the 3.5RC1 release of the
> Eclipse platform, I get a failure for one
> of the components:
>
> [java] org.eclipse.core.runtime.CoreException: The project cannot be
> built until its prerequisite com.ibm.icu is built. Cleaning and building
> all projects is recommended
> [java] at
> org.eclipse.buckminster.core.internal.actor.AbstractBuildInt egrationActor.internalPerform(AbstractBuildIntegrationActor. java:53)
>
> [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:198)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
>
> [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:79)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:618)
> [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] The project cannot be built until its prerequisite
> com.ibm.icu is built. Cleaning and building all projects is recommended
>
>
> Previously, everything has resolved correctly, so all of the plugins
> that are needed are in place as far as Buckminster is concerned.
> I took the offending project out of the build, and carried on, but in
> then another project would fail in a similar fashion. I eventually brought
> the build down to a single sub-project, but that also failed in the same
> manner, but citing a different plugin (org.jdom) as the one that needed
> to be built.
> The only common behaviour I see is that each time the 'cannot be built'
> issue refers to a prerequisite that is part of Orbit, which is read using
> eclipse.import from a remote map file:
>
> <provider readerType="eclipse.import" componentTypes="osgi.bundle"
> mutable="false" source="false">
> <uri
> format=" http://download.eclipse.org/tools/orbit/downloads/drops/I200 90504052954/orbitBundles-I20090504052954.map"
> />
> </provider>
>
> the map file exists and is valid (and has been used for M7).
>
> To take the remote issue out of the picture, I downloaded Orbit as a
> whole and unzipped it locally, then used a provider with a file: URI:
>
> <provider readerType="eclipse.import" componentTypes="osgi.bundle"
> mutable="false" source="false">
> <uri format="{0}/orbit/eclipse">
> <bc:propertyRef key="project.root" />
> </uri>
> </provider>
>
> The required orbit plugins are materialized from the local file system
> into the local workspace as expected, however the "project cannot be
> built" happens at the end of the build.
>
> Easiest way to reproduce this is to do a build on the build.eclipse.org
> infrastructure. Check out the STP Policy sub-project build:
>
> svn co
> http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.policy-ed itor/org.eclipse.stp.policy/trunk/build
>
> cd build/policy
>
> Then run a successful build with:
>
> ant -Dbase.directory=`pwd`/m7
> -Dplatform=/shared/stp/platforms/3.5M7/eclipse build
>
> and then run a failed build with
>
> ant -Dbase.directory=`pwd`/mrc1
> -Dplatform=/shared/stp/platforms/3.5RC1/eclipse build
>
> The only thing that has changed is the platform - so I have to suspect
> that first and foremost. What could have changed here?
>
> --oh
>
>
>
>
>
>
|
|
|
|
|
|
| Re: Issue with Buckminster build after upgrade to Eclipse RC1 Platform [message #385469 is a reply to message #385468] |
Tue, 19 May 2009 11:49 |
|
I seem to be missing some properties. After the build has set all the preferences it outputs:
[echo] .... building ${project.name} p2 repository
[java] org.eclipse.buckminster.core.import '${project.cquery.file}'
[java] Doing full workspace refresh
[java] Waiting for jobs to end
[java] java.io.FileNotFoundException: /home/thhal/workspaces/stp/build/shared/${project.cquery.fil e} (No such file
or directory)
Any idea?
- thomas
Oisin Hurley wrote:
> Oisin Hurley wrote:
>
> Thomas Hallgren wrote:
>> I'll try to reproduce this locally. It's hard to do meaningful
>> debugging on the build machine.
>
> Unfortunately I haven't been able to debug locally, because the MacOS
> build is failing again - it worked for a bit, and then started
> failing with the usual 'java.lang.Object' not found. So, I've abandoned
> it and now just work on the Eclipse infrastructure.
>
>> I've been using buck 1.1.350.r10285 BTW
>
> I've updated to r10307, and the same issue occurs. On further
> investigation, it looks like the only Orbit bundles that are giving
> trouble are com.ibm.icu and org.jdom - the javax.* bundles appear to be
> ok. The only difference that I can spot so far is that the problematic
> bundles have a source bundle as well as a
> binary bundle in Orbit - but even when I remove the source bundles I
> still get the same error.
>
> --oh
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03176 seconds
] 
Search
Help
Register
Login
Home
