| Dealing with an Unbound class container during build [message #375567] |
Thu, 07 February 2008 06:21 |
Eclipse User |
|
|
|
I am creating a headless buckminster build for a subcomponent of the
STP project, and I've nearly got it (I think :) except for an error
regarding the classpath container:
eid.build:
[echo] .... building eid
[java] Error: file /Users/ohurley/Projects/2008/eid-build/oncemore/output
/working/build/workspace/plugins/org.eclipse.stp.eid.editor:
Unbound classpath container: 'JRE System Library [J2SE-1.5]' in project
'org.eclipse.stp.eid.editor'
I've cut the error output - it is the same for each plugin in the
component.
The .classpath file for the plugin contains
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/o
rg.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2S E-1.5 "/>
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
<classpathentry kind="output" path="bin"/>
</classpath>
and of course the IDE build is fine :) I am making a guess that
perhaps I have missed out on a configuration setting in the buckminster
build.
When setting the buckminster preference for the target platform, I
use
org.eclipse.buckminster.jdt.complianceLevel = 1.5
To reproduce:
svn co http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.eid/trunk /build
cd build
ant -Dbase.directory=/tmp/build
-Dpde.target.arch=x86 # put your own arch here
-Dpde.target.nl=en_US
-Dpde.target.os=macosx # put your own os here
-Dpde.target.platform.path=... # location of your eclipse here
-Dpde.target.ws=carbon # put your window sys here
build
cheers
--oh
--
Oisin Hurley at IONA
http://blogs.iona.com/ohurley/
|
|
|
Powered by
FUDForum. Page generated in 0.03628 seconds
Home