On 7/19/07, Wayne Fay [EMAIL PROTECTED] wrote:
You should be able to put the java6 exec in front of java4 in your
PATH pretty trivially. Just put that EXPORT command in .bashrc or
equivalent for your user and never worry about it again.
Wayne
That exactly what I did in my .profile file and
On 7/19/07, Jeff Mutonho [EMAIL PROTECTED] wrote:
On 7/19/07, Wayne Fay [EMAIL PROTECTED] wrote:
You should be able to put the java6 exec in front of java4 in your
PATH pretty trivially. Just put that EXPORT command in .bashrc or
equivalent for your user and never worry about it again.
What shell are you running? (echo $SHELL or echo $0) Hmm oh wait, I
see you're running bash-2.05. I was going to suggest that you might be
running tcsh or csh where you'd use set rather than export.
Can you check /etc/passwd to confirm that your user account has bash
as its shell (/bin/bash) --
On 7/18/07, Henry Isidro [EMAIL PROTECTED] wrote:
Try changing your java alternative setting:
sudo update-alternatives --config java
HTH,
Henry
Hmmmit's running on a Solaris machine
-
To unsubscribe, e-mail: [EMAIL
ouch, is there something similar in Solaris?
Jeff Mutonho wrote:
On 7/18/07, Henry Isidro [EMAIL PROTECTED] wrote:
Try changing your java alternative setting:
sudo update-alternatives --config java
HTH,
Henry
Hmmmit's running on a Solaris machine
You should be able to put the java6 exec in front of java4 in your
PATH pretty trivially. Just put that EXPORT command in .bashrc or
equivalent for your user and never worry about it again.
Wayne
On 7/18/07, Henry Isidro [EMAIL PROTECTED] wrote:
ouch, is there something similar in Solaris?
My maven builds have been working without issue and now all of a
sudden they've started failing with the message :
started
$ java -cp
/app/maven/apache-tomcat-6.0.10/webapps/hudson/WEB-INF/lib/maven-agent-1.113.jar:/app/maven/M2/maven-2.0.4/core/boot/classworlds-1.1.jar
hudson.maven.agent.Main
Hi,
Try executing 'which java' from the command line and trace from this
which java (the one displayed may be an alternate only) is being
executed to verify if the java you're using is really 1.6. It might not
exactly be a Maven problem :-)
HTH,
Deng
Jeff Mutonho wrote:
My maven builds
On 7/17/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
Hi,
Try executing 'which java' from the command line and trace from this
which java (the one displayed may be an alternate only) is being
executed to verify if the java you're using is really 1.6. It might not
exactly be a Maven problem :-)
Try changing your java alternative setting:
sudo update-alternatives --config java
HTH,
Henry
Jeff Mutonho wrote:
On 7/17/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
Hi,
Try executing 'which java' from the command line and trace from this
which java (the one displayed may be an alternate
10 matches
Mail list logo