| Plug-in org.eclipse.buckminster.jarprocessor was unable to load class org.eclips [message #385133] |
Thu, 07 May 2009 06:55  |
Eclipse User |
|
|
|
I've made progress on the build, and can now construct a plain
p2 site (except for one feature, which causes the build to hang,
more on that later).
The next issue is around pack200 packing the site. I've simply
added site.pack200=true to the build instruction:
<buckminster command="org.eclipse.buckminster.core.perform">
<args>
<arg
value=" -Dbuckminster.output.root=${base.directory}/${project.name}. site "/>
<arg value="-Dsite.pack200=true"/>
<arg value="-Dcbi.include.source=false"/>
<arg value="-Dsite.signing=false"/>
<arg value="${project.toplevel.feature}#site.p2"/>
</args>
</buckminster>
(all this information was gleaned from Henrik's presentation
at EclipseCon, so perhaps I'm missing out something?)
An unusual error occurred
[start
org.eclipse.stp.toplevel.feature:eclipse.feature$2.0.0.20090 5070221#OSGi#copy.plugins]
..
..
[end
org.eclipse.stp.toplevel.feature:eclipse.feature$2.0.0.20090 5070221#OSGi#copy.plugins]
Doing full workspace refresh
Waiting for jobs to end
org.eclipse.core.runtime.CoreException: Plug-in
org.eclipse.buckminster.jarprocessor was unable to load class
org.eclipse.buckminster.jarprocessor.JarProcessorActor.
Further down we see the reason
Plug-in org.eclipse.buckminster.jarprocessor was unable to load class
org.eclipse.buckminster.jarprocessor.JarProcessorActor.
Caused by: java.lang.UnsupportedClassVersionError:
(org/eclipse/buckminster/jarprocessor/JarProcessorActor) bad major version
at offset=6
Normally you would see this when a 1.5-compiled class attempts to
load in a 1.4 VM. I do have jdt.complianceLevel set to 1.5, and lsprefs
confirms that before the perform task is run.
I'm not sure what could be causing it - is there perhaps something
I've neglected to add to the buckminster installation, some feature?
Are there any examples out there of this approach?
--oh
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04151 seconds
Home