|
Re: installJRE and IBM j9 [message #517833 is a reply to message #517832] |
Tue, 02 March 2010 05:06 |
|
Hi Markus,
We just call on the jdt the same way the IDE does when you install a JRE there. Can you install the JRE in question
using the IDE? From the looks of it, an attempt is made to execute some unix command. Is the JRE you're using runnable
on the platform where you attempt the install?
- thomas
On 03/02/2010 10:20 AM, Markus Alexander Kuppe wrote:
> Hi,
>
> does Bucky (installJRE) support non Sun JDKs, e.g. CDC1.x/Foundation1.x.
> With IBM j9 Bucky throws an exception. Pointing to the .ee (Execution
> Environment) file directly doesn't help either.
>
> 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
>
> P.S.: I assume http://www.eclipse.org/forums/index.php?t=tree&th=162762
> has been missed.
|
|
|
Re: installJRE and IBM j9 [message #517870 is a reply to message #517833] |
Tue, 02 March 2010 07:08 |
Eclipse User |
|
|
|
Originally posted by: news.eclipse.org.08.lemmster.de
On 03/02/2010 10:29 AM, Thomas Hallgren wrote:
> Hi Markus,
> We just call on the jdt the same way the IDE does when you install a JRE
> there. Can you install the JRE in question using the IDE? From the looks
> of it, an attempt is made to execute some unix command. Is the JRE
> you're using runnable on the platform where you attempt the install?
The same JRE works perfectly in the IDE when set up via "Execution
Environment Description" and pointing to the .ee file.
Markus
|
|
|
Re: installJRE and IBM j9 [message #517871 is a reply to message #517870] |
Tue, 02 March 2010 07:08 |
|
On 03/02/2010 12:49 PM, Markus Kuppe wrote:
> On 03/02/2010 10:29 AM, Thomas Hallgren wrote:
>> Hi Markus,
>> We just call on the jdt the same way the IDE does when you install a JRE
>> there. Can you install the JRE in question using the IDE? From the looks
>> of it, an attempt is made to execute some unix command. Is the JRE
>> you're using runnable on the platform where you attempt the install?
>
> The same JRE works perfectly in the IDE when set up via "Execution
> Environment Description" and pointing to the .ee file.
>
Very odd. AFAICS, the IDE calls the exact same function to install the JRE. I suggest you raise a bug against JDT where
you attach the stack-trace.
Regards,
Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.07051 seconds