Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5'
How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #514858] Tue, 16 February 2010 21:51 Go to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi,
I run the build on hudson on build.eclipse.org. I see these warnings:
[java] Warning: file
/opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
line 9: The JRE container on the classpath is not a perfect match to the 'J2SE-1.5' execution environment

In the configuration of the build I have set java 5.0 jdk. I have a feeling that it has something to do with the setting
in the workspace. What did you do with the buckminster build to solve/prevent this?

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #514874 is a reply to message #514858] Tue, 16 February 2010 23:27 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 02/16/2010 10:51 PM, Martin Taal wrote:
> Hi,
> I run the build on hudson on build.eclipse.org. I see these warnings:
> [java] Warning: file
> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
> line 9: The JRE container on the classpath is not a perfect match to the
> 'J2SE-1.5' execution environment
>
> In the configuration of the build I have set java 5.0 jdk. I have a
> feeling that it has something to do with the setting in the workspace.
> What did you do with the buckminster build to solve/prevent this?
>
We install the needed JRE in our workspace prior to building. In the ant build.xml that drives our build, you'll find this:

<buckminster command="installJRE">
<cmdargs>
<arg value="--location" />
<arg value="${jdk1.4.dir}" />
</cmdargs>
</buckminster>

The ${jdk1.4.dir} is the absolute path of the JRE. You can install any number of JRE's this way.

Regards,
Thomas Hallgren
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #515021 is a reply to message #514874] Wed, 17 February 2010 13:36 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Hi Thomas,

I am still getting this exception. I have this in the log (when running in debug mode):
[echo] Using workspace /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace
[echo] Setting jre to /shared/common/ibm-java2-ppc-50
[java] installJRE '-P' '/tmp/build-709667201.properties' '--location' '/shared/common/ibm-java2-ppc-50'
[java] Downloading file:/tmp/build-709667201.properties
[java] Doing full workspace refresh
[java] Waiting for jobs to end

This is part of the build script:

<echo message="Setting jre to ${env.JAVA_HOME}"/>
<buckminster command="installJRE" workspace="${workspacePath}">
<cmdargs>
<arg value="--location" />
<arg value="${env.JAVA_HOME}" />
</cmdargs>
</buckminster>

I do this before setting the target path, is that correct?
Does the 'doing full workspace refresh' have any influence on this?

See here for the complete log:
https://build.eclipse.org/hudson/job/emf-teneo-nightly/76/co nsoleFull

gr. Martin

Thomas Hallgren wrote:
> On 02/16/2010 10:51 PM, Martin Taal wrote:
>> Hi,
>> I run the build on hudson on build.eclipse.org. I see these warnings:
>> [java] Warning: file
>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
>>
>> line 9: The JRE container on the classpath is not a perfect match to the
>> 'J2SE-1.5' execution environment
>>
>> In the configuration of the build I have set java 5.0 jdk. I have a
>> feeling that it has something to do with the setting in the workspace.
>> What did you do with the buckminster build to solve/prevent this?
>>
> We install the needed JRE in our workspace prior to building. In the ant
> build.xml that drives our build, you'll find this:
>
> <buckminster command="installJRE">
> <cmdargs>
> <arg value="--location" />
> <arg value="${jdk1.4.dir}" />
> </cmdargs>
> </buckminster>
>
> The ${jdk1.4.dir} is the absolute path of the JRE. You can install any
> number of JRE's this way.
>
> Regards,
> Thomas Hallgren


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #515022 is a reply to message #515021] Wed, 17 February 2010 13:37 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
To be more precise in my wording :-), it is not an exception but a warning ofcourse.

gr. Martin

Martin Taal wrote:
> Hi Thomas,
>
> I am still getting this exception. I have this in the log (when running
> in debug mode):
> [echo] Using workspace
> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace
>
> [echo] Setting jre to /shared/common/ibm-java2-ppc-50
> [java] installJRE '-P' '/tmp/build-709667201.properties'
> '--location' '/shared/common/ibm-java2-ppc-50'
> [java] Downloading file:/tmp/build-709667201.properties
> [java] Doing full workspace refresh
> [java] Waiting for jobs to end
>
> This is part of the build script:
>
> <echo message="Setting jre to ${env.JAVA_HOME}"/>
> <buckminster command="installJRE" workspace="${workspacePath}">
> <cmdargs>
> <arg value="--location" />
> <arg value="${env.JAVA_HOME}" />
> </cmdargs>
> </buckminster>
>
> I do this before setting the target path, is that correct?
> Does the 'doing full workspace refresh' have any influence on this?
>
> See here for the complete log:
> https://build.eclipse.org/hudson/job/emf-teneo-nightly/76/co nsoleFull
>
> gr. Martin
>
> Thomas Hallgren wrote:
>> On 02/16/2010 10:51 PM, Martin Taal wrote:
>>> Hi,
>>> I run the build on hudson on build.eclipse.org. I see these warnings:
>>> [java] Warning: file
>>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
>>>
>>> line 9: The JRE container on the classpath is not a perfect match to the
>>> 'J2SE-1.5' execution environment
>>>
>>> In the configuration of the build I have set java 5.0 jdk. I have a
>>> feeling that it has something to do with the setting in the workspace.
>>> What did you do with the buckminster build to solve/prevent this?
>>>
>> We install the needed JRE in our workspace prior to building. In the
>> ant build.xml that drives our build, you'll find this:
>>
>> <buckminster command="installJRE">
>> <cmdargs>
>> <arg value="--location" />
>> <arg value="${jdk1.4.dir}" />
>> </cmdargs>
>> </buckminster>
>>
>> The ${jdk1.4.dir} is the absolute path of the JRE. You can install any
>> number of JRE's this way.
>>
>> Regards,
>> Thomas Hallgren
>
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #515085 is a reply to message #515021] Wed, 17 February 2010 16:40 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Martin,
Perhaps you need to update the classpath for the project in question (the button just below where you add EE's in the
PDE manifest editor).

The "doing full workspace refresh" is not related. It's just an information that Buckminster ensures that your workspace
is in sync with the file system prior to exit.

- thomas

On 02/17/2010 02:36 PM, Martin Taal wrote:
> Hi Thomas,
>
> I am still getting this exception. I have this in the log (when running
> in debug mode):
> [echo] Using workspace
> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace
>
> [echo] Setting jre to /shared/common/ibm-java2-ppc-50
> [java] installJRE '-P' '/tmp/build-709667201.properties' '--location'
> '/shared/common/ibm-java2-ppc-50'
> [java] Downloading file:/tmp/build-709667201.properties
> [java] Doing full workspace refresh
> [java] Waiting for jobs to end
>
> This is part of the build script:
>
> <echo message="Setting jre to ${env.JAVA_HOME}"/>
> <buckminster command="installJRE" workspace="${workspacePath}">
> <cmdargs>
> <arg value="--location" />
> <arg value="${env.JAVA_HOME}" />
> </cmdargs>
> </buckminster>
>
> I do this before setting the target path, is that correct?
> Does the 'doing full workspace refresh' have any influence on this?
>
> See here for the complete log:
> https://build.eclipse.org/hudson/job/emf-teneo-nightly/76/co nsoleFull
>
> gr. Martin
>
> Thomas Hallgren wrote:
>> On 02/16/2010 10:51 PM, Martin Taal wrote:
>>> Hi,
>>> I run the build on hudson on build.eclipse.org. I see these warnings:
>>> [java] Warning: file
>>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
>>>
>>> line 9: The JRE container on the classpath is not a perfect match to the
>>> 'J2SE-1.5' execution environment
>>>
>>> In the configuration of the build I have set java 5.0 jdk. I have a
>>> feeling that it has something to do with the setting in the workspace.
>>> What did you do with the buckminster build to solve/prevent this?
>>>
>> We install the needed JRE in our workspace prior to building. In the
>> ant build.xml that drives our build, you'll find this:
>>
>> <buckminster command="installJRE">
>> <cmdargs>
>> <arg value="--location" />
>> <arg value="${jdk1.4.dir}" />
>> </cmdargs>
>> </buckminster>
>>
>> The ${jdk1.4.dir} is the absolute path of the JRE. You can install any
>> number of JRE's this way.
>>
>> Regards,
>> Thomas Hallgren
>
>
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #515145 is a reply to message #515085] Wed, 17 February 2010 21:24 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
Thanks Thomas, this indeed solved it!

gr. Martin

Thomas Hallgren wrote:
> Hi Martin,
> Perhaps you need to update the classpath for the project in question
> (the button just below where you add EE's in the PDE manifest editor).
>
> The "doing full workspace refresh" is not related. It's just an
> information that Buckminster ensures that your workspace is in sync with
> the file system prior to exit.
>
> - thomas
>
> On 02/17/2010 02:36 PM, Martin Taal wrote:
>> Hi Thomas,
>>
>> I am still getting this exception. I have this in the log (when running
>> in debug mode):
>> [echo] Using workspace
>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace
>>
>>
>> [echo] Setting jre to /shared/common/ibm-java2-ppc-50
>> [java] installJRE '-P' '/tmp/build-709667201.properties' '--location'
>> '/shared/common/ibm-java2-ppc-50'
>> [java] Downloading file:/tmp/build-709667201.properties
>> [java] Doing full workspace refresh
>> [java] Waiting for jobs to end
>>
>> This is part of the build script:
>>
>> <echo message="Setting jre to ${env.JAVA_HOME}"/>
>> <buckminster command="installJRE" workspace="${workspacePath}">
>> <cmdargs>
>> <arg value="--location" />
>> <arg value="${env.JAVA_HOME}" />
>> </cmdargs>
>> </buckminster>
>>
>> I do this before setting the target path, is that correct?
>> Does the 'doing full workspace refresh' have any influence on this?
>>
>> See here for the complete log:
>> https://build.eclipse.org/hudson/job/emf-teneo-nightly/76/co nsoleFull
>>
>> gr. Martin
>>
>> Thomas Hallgren wrote:
>>> On 02/16/2010 10:51 PM, Martin Taal wrote:
>>>> Hi,
>>>> I run the build on hudson on build.eclipse.org. I see these warnings:
>>>> [java] Warning: file
>>>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
>>>>
>>>>
>>>> line 9: The JRE container on the classpath is not a perfect match to
>>>> the
>>>> 'J2SE-1.5' execution environment
>>>>
>>>> In the configuration of the build I have set java 5.0 jdk. I have a
>>>> feeling that it has something to do with the setting in the workspace.
>>>> What did you do with the buckminster build to solve/prevent this?
>>>>
>>> We install the needed JRE in our workspace prior to building. In the
>>> ant build.xml that drives our build, you'll find this:
>>>
>>> <buckminster command="installJRE">
>>> <cmdargs>
>>> <arg value="--location" />
>>> <arg value="${jdk1.4.dir}" />
>>> </cmdargs>
>>> </buckminster>
>>>
>>> The ${jdk1.4.dir} is the absolute path of the JRE. You can install any
>>> number of JRE's this way.
>>>
>>> Regards,
>>> Thomas Hallgren
>>
>>
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: How to prevent: JRE container on the classpath is not a perfect match to the 'J2SE-1.5' [message #515528 is a reply to message #514874] Fri, 19 February 2010 09:29 Go to previous message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
On 02/17/2010 12:27 AM, Thomas Hallgren wrote:
> On 02/16/2010 10:51 PM, Martin Taal wrote:
>> Hi,
>> I run the build on hudson on build.eclipse.org. I see these warnings:
>> [java] Warning: file
>> /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/worksp ace/build/build/workspace/plugins/org.eclipse.emf.teneo.anno tations/META-INF/MANIFEST.MF,
>>
>> line 9: The JRE container on the classpath is not a perfect match to the
>> 'J2SE-1.5' execution environment
>>
>> In the configuration of the build I have set java 5.0 jdk. I have a
>> feeling that it has something to do with the setting in the workspace.
>> What did you do with the buckminster build to solve/prevent this?
>>
> We install the needed JRE in our workspace prior to building. In the ant
> build.xml that drives our build, you'll find this:
>
> <buckminster command="installJRE">
> <cmdargs>
> <arg value="--location" />
> <arg value="${jdk1.4.dir}" />
> </cmdargs>
> </buckminster>
>
> The ${jdk1.4.dir} is the absolute path of the JRE. You can install any
> number of JRE's this way.

Is installJRE supposed to support IBM's j9 as well? If I try to set it
to j9 it results with an exception.

ecf2:/opt/toolbox/eclipse.org/buckminster/r11191 # ./buckminster
installJRE --location /opt/toolbox/ibm.com/j9/j9_6.1.1.20061110-161633/
ERROR: Exception occurred executing command line.
org.eclipse.core.runtime.CoreException: Exception occurred executing
command line.
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:814 )
at
org.eclipse.jdt.internal.launching.StandardVMType.generateLi braryInfo(StandardVMType.java:500)
at
org.eclipse.jdt.internal.launching.StandardVMType.getLibrary Info(StandardVMType.java:122)
at
org.eclipse.jdt.internal.launching.StandardVMType.getDefault LibraryLocations(StandardVMType.java:290)
at
org.eclipse.jdt.internal.launching.StandardVMType.canDetectD efaultSystemLibraries(StandardVMType.java:140)
at
org.eclipse.jdt.internal.launching.StandardVMType.validateIn stallLocation(StandardVMType.java:452)
at
org.eclipse.buckminster.jdt.commands.InstallJRE.internalRun( InstallJRE.java:82)
at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: java.io.IOException: java.io.IOException:
/opt/toolbox/ibm.com/j9/j9_6.1.1.20061110-161633/bin/j9: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:507)
at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:808 )
... 24 more

The directory layout of the j9 is like:

ecf2:/opt/toolbox/ibm.com/j9/j9_6.1.1.20061110-161633 # ls -la
total 36
drwxr-xr-x 6 root root 4096 Jan 22 2009 .
drwxr-xr-x 3 root root 4096 Jan 22 2009 ..
-rw-r--r-- 1 mkuppe cimasters 939 Jan 22 2009 CDC1-1_Foundation1-1.ee
drwxr-xr-x 5 mkuppe cimasters 4096 Jan 22 2009 bin
-rw-r--r-- 1 mkuppe cimasters 710 Nov 10 2006 buildinfo.xml
-rw-r--r-- 1 mkuppe cimasters 222 Nov 10 2006 copyright.txt
drwxr-xr-x 2 mkuppe cimasters 4096 Jan 22 2009 doc
drwxr-xr-x 2 mkuppe cimasters 4096 Jan 22 2009 examples
drwxr-xr-x 4 mkuppe cimasters 4096 Jan 22 2009 lib


Thanks
Markus
Previous Topic:More bucky 3.6 p2 agent trouble...
Next Topic:Is there support form properties in an Aggregator model?
Goto Forum:
  


Current Time: Fri Apr 20 01:25:16 GMT 2018

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

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