v1.104 not using JAVA_HOME for maven 2 JVM

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

v1.104 not using JAVA_HOME for maven 2 JVM

J. Matthew Pryor-2
I just upgraded to v1.104 and my builds are now failing.

The linux box I am using has gcj on the command-line, and hudson does not seem to use JAVA_HOME to find the JVM executable

started
$ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/classworlds-1.1.jar hudson.maven.agent.Main /usr/local/maven/maven-2.0.6 /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/remoting-1.104.jar /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-interceptor-1.104.jar
Exception in thread "main" java.lang.NoClassDefFoundError: hudson.remoting.Launcher
   at java.lang.Class.initializeClass(libgcj.so.70)
   at java.lang.reflect.Method.invoke(libgcj.so.70)
   at hudson.maven.agent.Main.main(Main.java:62)
   at hudson.maven.agent.Main.main(Main.java:31)
Caused by: java.lang.ClassNotFoundException: java.util.concurrent.Executor not found in org.codehaus.classworlds.RealmClassLoader{urls=[file:/var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-interceptor-1.104.jar,file:/usr/local/maven/maven-2.0.6/lib/maven-core-2.0.6-uber.jar], parent=null}
   at java.net.URLClassLoader.findClass(libgcj.so.70)
   at java.lang.ClassLoader.loadClass(libgcj.so.70)
   at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
   at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
   at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
   at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
   at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
   at java.lang.ClassLoader.loadClass(libgcj.so.70)
   at java.lang.Class.initializeClass(libgcj.so.70)
   ...3 more
FATAL: unexpected stream termination
java.io.EOFException: unexpected stream termination
at hudson.remoting.Channel.<init>(Channel.java:142)
at hudson.Launcher$LocalLauncher$1.<init>(Launcher.java:183)
at hudson.Launcher$LocalLauncher.launchChannel(Launcher.java:182)
at hudson.maven.MavenBuild$RunnerImpl.newProcess(MavenBuild.java:288)
at hudson.maven.ProcessCache.get(ProcessCache.java:166)
at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:257)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:121)
at hudson.model.Run.run(Run.java:559)
at hudson.maven.MavenBuild.run(MavenBuild.java:127)
at hudson.model.Executor.run(Executor.java:59)

I have configured JAVA_HOME as a JVM, is there something I am missing?

Thanks,
Matthew

Reply | Threaded
Open this post in threaded view
|

Re: v1.104 not using JAVA_HOME for maven 2 JVM

Kohsuke Kawaguchi
Administrator
J. Matthew Pryor wrote:
> I just upgraded to v1.104 and my builds are now failing.
>
> The linux box I am using has gcj on the command-line, and hudson does  
> not seem to use JAVA_HOME to find the JVM executable

Can you enable the debug probe that I suggested earlier?

   hudson.maven.MavenBuild.debug=true;

from the scripting console.

>
> started
> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-
> agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/classworlds-1.1.jar  
> hudson.maven.agent.Main /usr/local/maven/maven-2.0.6 /var/lib/
> tomcat5.5/webapps/hudson/WEB-INF/lib/remoting-1.104.jar /var/lib/
> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-interceptor-1.104.jar
> Exception in thread "main" java.lang.NoClassDefFoundError:  
> hudson.remoting.Launcher
>     at java.lang.Class.initializeClass(libgcj.so.70)
>     at java.lang.reflect.Method.invoke(libgcj.so.70)
>     at hudson.maven.agent.Main.main(Main.java:62)
>     at hudson.maven.agent.Main.main(Main.java:31)
> Caused by: java.lang.ClassNotFoundException:  
> java.util.concurrent.Executor not found in  
> org.codehaus.classworlds.RealmClassLoader{urls=[file:/var/lib/
> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-
> interceptor-1.104.jar,file:/usr/local/maven/maven-2.0.6/lib/maven-
> core-2.0.6-uber.jar], parent=null}
>     at java.net.URLClassLoader.findClass(libgcj.so.70)
>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>     at org.codehaus.classworlds.RealmClassLoader.loadClassDirect
> (RealmClassLoader.java:195)
>     at org.codehaus.classworlds.DefaultClassRealm.loadClass
> (DefaultClassRealm.java:255)
>     at org.codehaus.classworlds.DefaultClassRealm.loadClass
> (DefaultClassRealm.java:274)
>     at org.codehaus.classworlds.DefaultClassRealm.loadClass
> (DefaultClassRealm.java:274)
>     at org.codehaus.classworlds.RealmClassLoader.loadClass
> (RealmClassLoader.java:214)
>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>     at java.lang.Class.initializeClass(libgcj.so.70)
>     ...3 more
> FATAL: unexpected stream termination
> java.io.EOFException: unexpected stream termination
> at hudson.remoting.Channel.<init>(Channel.java:142)
> at hudson.Launcher$LocalLauncher$1.<init>(Launcher.java:183)
> at hudson.Launcher$LocalLauncher.launchChannel(Launcher.java:182)
> at hudson.maven.MavenBuild$RunnerImpl.newProcess(MavenBuild.java:288)
> at hudson.maven.ProcessCache.get(ProcessCache.java:166)
> at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:257)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
> 121)
> at hudson.model.Run.run(Run.java:559)
> at hudson.maven.MavenBuild.run(MavenBuild.java:127)
> at hudson.model.Executor.run(Executor.java:59)
>
> I have configured JAVA_HOME as a JVM, is there something I am missing?
>
> Thanks,
> Matthew
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: v1.104 not using JAVA_HOME for maven 2 JVM

J. Matthew Pryor-2
DEBUG OUTPUT
======

started
Reporters=[hudson.maven.reporters.MavenMailer@f0b9d0,  
hudson.maven.reporters.MavenArtifactArchiver@b9a3db,  
hudson.maven.reporters.MavenFingerprinter@1b4b7a7,  
hudson.maven.reporters.MavenJavadocArchiver@1856501,  
hudson.maven.reporters.SurefireArchiver@aa2675,  
hudson.maven.reporters.BuildInfoRecorder@c2e135]
Using env variables: {JOB_NAME=au.com.observant:observant-elvis,  
HUDSON_HOME=/usr/share/tomcat5.5/.hudson, BUILD_NUMBER=95,  
BUILD_TAG=hudson-au.com.observant:observant-elvis-95, JAVA_HOME=/usr/
local/lib/jdk, PATH+JDK=/usr/local/lib/jdk/bin,  
BUILD_ID=2007-04-24_09-07-28, EXECUTOR_NUMBER=0}
$ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-
agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/classworlds-1.1.jar  
hudson.maven.agent.Main /usr/local/maven/maven-2.0.6 /var/lib/
tomcat5.5/webapps/hudson/WEB-INF/lib/remoting-1.104.jar /var/lib/
tomcat5.5/webapps/hudson/WEB-INF/lib/maven-interceptor-1.104.jar
channel started

====

For now I have manually changed the script that starts up tomcat to  
put the Sun JDK path in front of /usr/bin which is where GCJ is.

It look st me like the command being used:

$ java -cp <SNIP>

Is relying on the PATH of the user that Tomcat is running as,  
shouldn't it be something like

$JAVA_HOME/bin/java -cp <SNIP>

Thanks,
Matthew

On 24/04/2007, at 7:39 AM, Kohsuke Kawaguchi wrote:

> J. Matthew Pryor wrote:
>> I just upgraded to v1.104 and my builds are now failing.
>> The linux box I am using has gcj on the command-line, and hudson  
>> does  not seem to use JAVA_HOME to find the JVM executable
>
> Can you enable the debug probe that I suggested earlier?
>
>   hudson.maven.MavenBuild.debug=true;
>
> from the scripting console.
>
>> started
>> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>> agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/
>> classworlds-1.1.jar  hudson.maven.agent.Main /usr/local/maven/
>> maven-2.0.6 /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>> remoting-1.104.jar /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>> maven-interceptor-1.104.jar
>> Exception in thread "main" java.lang.NoClassDefFoundError:  
>> hudson.remoting.Launcher
>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>     at java.lang.reflect.Method.invoke(libgcj.so.70)
>>     at hudson.maven.agent.Main.main(Main.java:62)
>>     at hudson.maven.agent.Main.main(Main.java:31)
>> Caused by: java.lang.ClassNotFoundException:  
>> java.util.concurrent.Executor not found in  
>> org.codehaus.classworlds.RealmClassLoader{urls=[file:/var/lib/  
>> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>> interceptor-1.104.jar,file:/usr/local/maven/maven-2.0.6/lib/maven-  
>> core-2.0.6-uber.jar], parent=null}
>>     at java.net.URLClassLoader.findClass(libgcj.so.70)
>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>     at org.codehaus.classworlds.RealmClassLoader.loadClassDirect  
>> (RealmClassLoader.java:195)
>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>> (DefaultClassRealm.java:255)
>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>> (DefaultClassRealm.java:274)
>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>> (DefaultClassRealm.java:274)
>>     at org.codehaus.classworlds.RealmClassLoader.loadClass  
>> (RealmClassLoader.java:214)
>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>     ...3 more
>> FATAL: unexpected stream termination
>> java.io.EOFException: unexpected stream termination
>> at hudson.remoting.Channel.<init>(Channel.java:142)
>> at hudson.Launcher$LocalLauncher$1.<init>(Launcher.java:183)
>> at hudson.Launcher$LocalLauncher.launchChannel(Launcher.java:182)
>> at hudson.maven.MavenBuild$RunnerImpl.newProcess(MavenBuild.java:
>> 288)
>> at hudson.maven.ProcessCache.get(ProcessCache.java:166)
>> at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:257)
>> at hudson.model.AbstractBuild$AbstractRunner.run
>> (AbstractBuild.java: 121)
>> at hudson.model.Run.run(Run.java:559)
>> at hudson.maven.MavenBuild.run(MavenBuild.java:127)
>> at hudson.model.Executor.run(Executor.java:59)
>> I have configured JAVA_HOME as a JVM, is there something I am  
>> missing?
>> Thanks,
>> Matthew
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: v1.104 not using JAVA_HOME for maven 2 JVM

Kohsuke Kawaguchi
Administrator
J. Matthew Pryor wrote:

> DEBUG OUTPUT
> ======
>
> started
> Reporters=[hudson.maven.reporters.MavenMailer@f0b9d0,  
> hudson.maven.reporters.MavenArtifactArchiver@b9a3db,  
> hudson.maven.reporters.MavenFingerprinter@1b4b7a7,  
> hudson.maven.reporters.MavenJavadocArchiver@1856501,  
> hudson.maven.reporters.SurefireArchiver@aa2675,  
> hudson.maven.reporters.BuildInfoRecorder@c2e135]
> Using env variables: {JOB_NAME=au.com.observant:observant-elvis,  
> HUDSON_HOME=/usr/share/tomcat5.5/.hudson, BUILD_NUMBER=95,  
> BUILD_TAG=hudson-au.com.observant:observant-elvis-95, JAVA_HOME=/usr/
> local/lib/jdk, PATH+JDK=/usr/local/lib/jdk/bin,  
> BUILD_ID=2007-04-24_09-07-28, EXECUTOR_NUMBER=0}
> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-
> agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/classworlds-1.1.jar  
> hudson.maven.agent.Main /usr/local/maven/maven-2.0.6 /var/lib/
> tomcat5.5/webapps/hudson/WEB-INF/lib/remoting-1.104.jar /var/lib/
> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-interceptor-1.104.jar
> channel started
>
> ====
 From what I can tell, this is actually working correctly. It sets the
right JAVA_HOME, and "PATH+JDK" is a special notation that says "let's
prepend this value to PATH right before we launch".

So the newly launched process should have /usr/local/lib/jdk/bin at the
beginning of PATH. That effectively causes "java" to be come
$JAVA_HOME/bin/java.

... or wait, it doesn't! If I say Runtime.exec("java"), PATH of Tomcat
is searched, obviously not PATH of the newly launched process.

So that's why!

> For now I have manually changed the script that starts up tomcat to  
> put the Sun JDK path in front of /usr/bin which is where GCJ is.
>
> It look st me like the command being used:
>
> $ java -cp <SNIP>
>
> Is relying on the PATH of the user that Tomcat is running as,  
> shouldn't it be something like
>
> $JAVA_HOME/bin/java -cp <SNIP>


>
> Thanks,
> Matthew
>
> On 24/04/2007, at 7:39 AM, Kohsuke Kawaguchi wrote:
>
>> J. Matthew Pryor wrote:
>>> I just upgraded to v1.104 and my builds are now failing.
>>> The linux box I am using has gcj on the command-line, and hudson  
>>> does  not seem to use JAVA_HOME to find the JVM executable
>>
>> Can you enable the debug probe that I suggested earlier?
>>
>>   hudson.maven.MavenBuild.debug=true;
>>
>> from the scripting console.
>>
>>> started
>>> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>>> agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/
>>> classworlds-1.1.jar  hudson.maven.agent.Main /usr/local/maven/
>>> maven-2.0.6 /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>>> remoting-1.104.jar /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>>> maven-interceptor-1.104.jar
>>> Exception in thread "main" java.lang.NoClassDefFoundError:  
>>> hudson.remoting.Launcher
>>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>>     at java.lang.reflect.Method.invoke(libgcj.so.70)
>>>     at hudson.maven.agent.Main.main(Main.java:62)
>>>     at hudson.maven.agent.Main.main(Main.java:31)
>>> Caused by: java.lang.ClassNotFoundException:  
>>> java.util.concurrent.Executor not found in  
>>> org.codehaus.classworlds.RealmClassLoader{urls=[file:/var/lib/  
>>> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>>> interceptor-1.104.jar,file:/usr/local/maven/maven-2.0.6/lib/maven-  
>>> core-2.0.6-uber.jar], parent=null}
>>>     at java.net.URLClassLoader.findClass(libgcj.so.70)
>>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>>     at org.codehaus.classworlds.RealmClassLoader.loadClassDirect  
>>> (RealmClassLoader.java:195)
>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>> (DefaultClassRealm.java:255)
>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>> (DefaultClassRealm.java:274)
>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>> (DefaultClassRealm.java:274)
>>>     at org.codehaus.classworlds.RealmClassLoader.loadClass  
>>> (RealmClassLoader.java:214)
>>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>>     ...3 more
>>> FATAL: unexpected stream termination
>>> java.io.EOFException: unexpected stream termination
>>> at hudson.remoting.Channel.<init>(Channel.java:142)
>>> at hudson.Launcher$LocalLauncher$1.<init>(Launcher.java:183)
>>> at hudson.Launcher$LocalLauncher.launchChannel(Launcher.java:182)
>>> at hudson.maven.MavenBuild$RunnerImpl.newProcess(MavenBuild.java:
>>> 288)
>>> at hudson.maven.ProcessCache.get(ProcessCache.java:166)
>>> at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:257)
>>> at hudson.model.AbstractBuild$AbstractRunner.run
>>> (AbstractBuild.java: 121)
>>> at hudson.model.Run.run(Run.java:559)
>>> at hudson.maven.MavenBuild.run(MavenBuild.java:127)
>>> at hudson.model.Executor.run(Executor.java:59)
>>> I have configured JAVA_HOME as a JVM, is there something I am  
>>> missing?
>>> Thanks,
>>> Matthew
>>
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                   [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: v1.104 not using JAVA_HOME for maven 2 JVM

J. Matthew Pryor-2
In reply to this post by J. Matthew Pryor-2
So is this a bug then?
Thanks,
Matthew

>
> On 25/04/2007, at 12:54 AM, Kohsuke Kawaguchi wrote:
>
>> J. Matthew Pryor wrote:
>>> DEBUG OUTPUT
>>> ======
>>> started
>>> Reporters=[hudson.maven.reporters.MavenMailer@f0b9d0,  
>>> hudson.maven.reporters.MavenArtifactArchiver@b9a3db,  
>>> hudson.maven.reporters.MavenFingerprinter@1b4b7a7,  
>>> hudson.maven.reporters.MavenJavadocArchiver@1856501,  
>>> hudson.maven.reporters.SurefireArchiver@aa2675,  
>>> hudson.maven.reporters.BuildInfoRecorder@c2e135]
>>> Using env variables: {JOB_NAME=au.com.observant:observant-elvis,  
>>> HUDSON_HOME=/usr/share/tomcat5.5/.hudson, BUILD_NUMBER=95,  
>>> BUILD_TAG=hudson-au.com.observant:observant-elvis-95, JAVA_HOME=/
>>> usr/ local/lib/jdk, PATH+JDK=/usr/local/lib/jdk/bin,  
>>> BUILD_ID=2007-04-24_09-07-28, EXECUTOR_NUMBER=0}
>>> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>>> agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/
>>> classworlds-1.1.jar  hudson.maven.agent.Main /usr/local/maven/
>>> maven-2.0.6 /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>>> remoting-1.104.jar /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/
>>> maven-interceptor-1.104.jar
>>> channel started
>>> ====
>>
>> From what I can tell, this is actually working correctly. It sets  
>> the right JAVA_HOME, and "PATH+JDK" is a special notation that  
>> says "let's prepend this value to PATH right before we launch".
>>
>> So the newly launched process should have /usr/local/lib/jdk/bin  
>> at the beginning of PATH. That effectively causes "java" to be  
>> come $JAVA_HOME/bin/java.
>>
>> ... or wait, it doesn't! If I say Runtime.exec("java"), PATH of  
>> Tomcat is searched, obviously not PATH of the newly launched process.
>>
>> So that's why!
>>
>>> For now I have manually changed the script that starts up tomcat  
>>> to  put the Sun JDK path in front of /usr/bin which is where GCJ is.
>>> It look st me like the command being used:
>>> $ java -cp <SNIP>
>>> Is relying on the PATH of the user that Tomcat is running as,  
>>> shouldn't it be something like
>>> $JAVA_HOME/bin/java -cp <SNIP>
>>
>>
>>
>>> Thanks,
>>> Matthew
>>> On 24/04/2007, at 7:39 AM, Kohsuke Kawaguchi wrote:
>>>> J. Matthew Pryor wrote:
>>>>> I just upgraded to v1.104 and my builds are now failing.
>>>>> The linux box I am using has gcj on the command-line, and  
>>>>> hudson  does  not seem to use JAVA_HOME to find the JVM executable
>>>>
>>>> Can you enable the debug probe that I suggested earlier?
>>>>
>>>>   hudson.maven.MavenBuild.debug=true;
>>>>
>>>> from the scripting console.
>>>>
>>>>> started
>>>>> $ java -cp /var/lib/tomcat5.5/webapps/hudson/WEB-INF/lib/
>>>>> maven-  agent-1.104.jar:/usr/local/maven/maven-2.0.6/boot/  
>>>>> classworlds-1.1.jar  hudson.maven.agent.Main /usr/local/maven/  
>>>>> maven-2.0.6 /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/lib/  
>>>>> remoting-1.104.jar /var/lib/ tomcat5.5/webapps/hudson/WEB-INF/
>>>>> lib/ maven-interceptor-1.104.jar
>>>>> Exception in thread "main" java.lang.NoClassDefFoundError:    
>>>>> hudson.remoting.Launcher
>>>>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>>>>     at java.lang.reflect.Method.invoke(libgcj.so.70)
>>>>>     at hudson.maven.agent.Main.main(Main.java:62)
>>>>>     at hudson.maven.agent.Main.main(Main.java:31)
>>>>> Caused by: java.lang.ClassNotFoundException:    
>>>>> java.util.concurrent.Executor not found in    
>>>>> org.codehaus.classworlds.RealmClassLoader{urls=[file:/var/lib/  
>>>>> tomcat5.5/webapps/hudson/WEB-INF/lib/maven-  
>>>>> interceptor-1.104.jar,file:/usr/local/maven/maven-2.0.6/lib/
>>>>> maven-  core-2.0.6-uber.jar], parent=null}
>>>>>     at java.net.URLClassLoader.findClass(libgcj.so.70)
>>>>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>>>>     at  
>>>>> org.codehaus.classworlds.RealmClassLoader.loadClassDirect  
>>>>> (RealmClassLoader.java:195)
>>>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>>>> (DefaultClassRealm.java:255)
>>>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>>>> (DefaultClassRealm.java:274)
>>>>>     at org.codehaus.classworlds.DefaultClassRealm.loadClass  
>>>>> (DefaultClassRealm.java:274)
>>>>>     at org.codehaus.classworlds.RealmClassLoader.loadClass  
>>>>> (RealmClassLoader.java:214)
>>>>>     at java.lang.ClassLoader.loadClass(libgcj.so.70)
>>>>>     at java.lang.Class.initializeClass(libgcj.so.70)
>>>>>     ...3 more
>>>>> FATAL: unexpected stream termination
>>>>> java.io.EOFException: unexpected stream termination
>>>>> at hudson.remoting.Channel.<init>(Channel.java:142)
>>>>> at hudson.Launcher$LocalLauncher$1.<init>(Launcher.java:183)
>>>>> at hudson.Launcher$LocalLauncher.launchChannel(Launcher.java:182)
>>>>> at hudson.maven.MavenBuild$RunnerImpl.newProcess
>>>>> (MavenBuild.java: 288)
>>>>> at hudson.maven.ProcessCache.get(ProcessCache.java:166)
>>>>> at hudson.maven.MavenBuild$RunnerImpl.doRun(MavenBuild.java:257)
>>>>> at hudson.model.AbstractBuild$AbstractRunner.run  
>>>>> (AbstractBuild.java: 121)
>>>>> at hudson.model.Run.run(Run.java:559)
>>>>> at hudson.maven.MavenBuild.run(MavenBuild.java:127)
>>>>> at hudson.model.Executor.run(Executor.java:59)
>>>>> I have configured JAVA_HOME as a JVM, is there something I am  
>>>>> missing?
>>>>> Thanks,
>>>>> Matthew
>>>>
>>>>
>>>> --
>>>> Kohsuke Kawaguchi
>>>> Sun Microsystems                   [hidden email]
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                   [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: v1.104 not using JAVA_HOME for maven 2 JVM

Kohsuke Kawaguchi
Administrator
Yes. This is already fixed for the next 1.105.

2007/4/29, J. Matthew Pryor <[hidden email]>:
> So is this a bug then?

--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]