Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Plug-in org.eclipse.buckminster.jarprocessor was unable to load class org.eclips
Plug-in org.eclipse.buckminster.jarprocessor was unable to load class org.eclips [message #385133] Thu, 07 May 2009 10:55 Go to next message
Oisin Hurley is currently offline Oisin HurleyFriend
Messages: 204
Registered: July 2009
Senior Member
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
Re: Plug-in org.eclipse.buckminster.jarprocessor was unable to load class org.eclips [message #385134 is a reply to message #385133] Thu, 07 May 2009 11:14 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Apparently, that class is compiled for target 1.6 and you're using Java 1.5. Very strange indeed, since the project
setting for the target compliance level is 1.5.

I'll investigate this further and include it in a new upload during the day today.

- thomas


Oisin Hurley wrote:
> 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
>
Re: Plug-in org.eclipse.buckminster.jarprocessor was unable to load [SOLUTION] [message #385135 is a reply to message #385134] Fri, 08 May 2009 00:13 Go to previous message
Oisin Hurley is currently offline Oisin HurleyFriend
Messages: 204
Registered: July 2009
Senior Member
This item is fixed in the r10280 build that is on the update site.

Thanks Thomas!

--oh
Previous Topic:"There is no active target platform" when setting buckminster preference
Next Topic:Signing jars with Buckminster
Goto Forum:
  


Current Time: Tue Apr 16 10:34:18 GMT 2024

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

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

Back to the top