Re: compiling under java 1.6.0_71

2014-02-05 Thread teilo
If you don't need jdk auto install then try using maven toolchains.
 Then run the job with whatever jdk works for maven and Jenkins

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: compiling under java 1.6.0_71

2014-02-05 Thread Stephen Connolly
Switching to a freestyle build with a maven build step should resolve the
issue as you can then run Jenkins with 1.7.0 and build using maven and the
older JDK

http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.htmlstrikes
again!


On 5 February 2014 14:20, marathiboy  wrote:

> Thanks Richard,
>
> I understand that Java 1.6.0_71 is NOT freely available, however, since I
> am
> just compiling (Jenkins's tomcat is running under Java 1.7), I thought this
> should show me compilation error from my code and never expected to see
> errors from Jenkins side.
>
> Due to COTS issue, we must stick to Java 1.6 and hence the problem.
>
> Thanks again
>
> S
>
>
>
> --
> View this message in context:
> http://jenkins-ci.361315.n4.nabble.com/compiling-under-java-1-6-0-71-tp4689274p4689357.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: compiling under java 1.6.0_71

2014-02-05 Thread marathiboy
Thanks Richard,

I understand that Java 1.6.0_71 is NOT freely available, however, since I am
just compiling (Jenkins's tomcat is running under Java 1.7), I thought this
should show me compilation error from my code and never expected to see
errors from Jenkins side.

Due to COTS issue, we must stick to Java 1.6 and hence the problem.

Thanks again

S



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/compiling-under-java-1-6-0-71-tp4689274p4689357.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: compiling under java 1.6.0_71

2014-02-04 Thread Richard Bywater
Unfortunately I'm not sure how many people will be able to help you out
given that Patch 71 isn't generally publicly available.

Richard.


On Wed, Feb 5, 2014 at 3:40 PM, Ligade, Shailesh [USA] <
ligade_shail...@bah.com> wrote:

>  Hello,
>
> We have to compile with java 1.6.0_71 and I am seeing this build issue.
> Not sure, if this is related to Jenkins, but since the error  states that,
> I just wanted to rule out that possibility.
>
> Appreciate, if anyone can tell me, how to get this compiled under 71
> (apparently 1.6.0_65 can compile).
>
> Thanks
>
> S
>
> ---
>
> Parsing POMs
> Modules changed, recalculating dependency graph
> [workspace] $ /usr/java/jdk1.6.0_71/bin/java -Xms1024m -Xmx1024m
> -XX:MaxPermSize=512m -Djavax.net.ssl.keyStoreType=PKCS11
> -Djavax.net.ssl.keyStore=NONE
> -Djavax.net.ssl.keyStoreProvider=SunPKCS11-FIPSProvider
> -Djavax.net.ssl.keyStorePassword=p...@ssw0rd-djavax.net.ssl.trustStore=/opt/apache-tomcat/conf/gnise-ci.jks
>  -cp
> /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.4.jar:/opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1/boot/classworlds-1.1.jar
> hudson.maven.agent.Main
> /opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1
> /opt/apache-tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/remoting-2.33.jar
> /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.4.jar
> 39000
> /opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar
> <===[JENKINS REMOTING CAPACITY]===>channel started
> ERROR: Processing failed due to a bug in the code. Please report this to
> jenkinsci-users@googlegroups.com
> *hudson.remoting.RequestAbortedException*:
> hudson.remoting.RequestAbortedException: java.io.InvalidClassException:
> [Ljava.lang.StackTraceElement;; serializable and externalizable flags
> conflict
> at
> *hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)*
> at
> *hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)*
> at 
> *hudson.remoting.Request.call(Request.java:174)*
> at 
> *hudson.remoting.Channel.call(Channel.java:722)*
> at
> *hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:257)*
> at 
> *hudson.maven.ProcessCache.get(ProcessCache.java:235)*
> at
> *hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:749)*
> at
> *hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)*
> at 
> *hudson.model.Run.execute(Run.java:1678)*
> at
> *hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)*
> at
> *hudson.model.ResourceController.execute(ResourceController.java:88)*
> at 
> *hudson.model.Executor.run(Executor.java:231)*
> Caused by: 
> *hudson.remoting.RequestAbortedException*:
> java.io.InvalidClassException: [Ljava.lang.StackTraceElement;; serializable
> and externalizable flags conflict
> at 
> *hudson.remoting.Request.abort(Request.java:299)*
> at 
> *hudson.remoting.Channel.terminate(Channel.java:782)*
> at 
> *hudson.slaves.Channels$1.terminate(Channels.java:77)*

compiling under java 1.6.0_71

2014-02-04 Thread Ligade, Shailesh [USA]
Hello,

We have to compile with java 1.6.0_71 and I am seeing this build issue. Not 
sure, if this is related to Jenkins, but since the error  states that, I just 
wanted to rule out that possibility.

Appreciate, if anyone can tell me, how to get this compiled under 71 
(apparently 1.6.0_65 can compile).

Thanks

S
---

Parsing POMs
Modules changed, recalculating dependency graph
[workspace] $ /usr/java/jdk1.6.0_71/bin/java -Xms1024m -Xmx1024m 
-XX:MaxPermSize=512m -Djavax.net.ssl.keyStoreType=PKCS11 
-Djavax.net.ssl.keyStore=NONE 
-Djavax.net.ssl.keyStoreProvider=SunPKCS11-FIPSProvider 
-Djavax.net.ssl.keyStorePassword=P@ssw0rd 
-Djavax.net.ssl.trustStore=/opt/apache-tomcat/conf/gnise-ci.jks -cp 
/opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.4.jar:/opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1/boot/classworlds-1.1.jar
 hudson.maven.agent.Main 
/opt/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1 
/opt/apache-tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/remoting-2.33.jar 
/opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.4.jar 39000 
/opt/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar
<===[JENKINS REMOTING CAPACITY]===>channel started
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-users@googlegroups.com
hudson.remoting.RequestAbortedException:
 hudson.remoting.RequestAbortedException: java.io.InvalidClassException: 
[Ljava.lang.StackTraceElement;; serializable and externalizable flags conflict
at 
hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
at 
hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
at 
hudson.remoting.Request.call(Request.java:174)
at 
hudson.remoting.Channel.call(Channel.java:722)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:257)
at 
hudson.maven.ProcessCache.get(ProcessCache.java:235)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:749)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)
at 
hudson.model.Run.execute(Run.java:1678)
at 
hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at 
hudson.model.ResourceController.execute(ResourceController.java:88)
at 
hudson.model.Executor.run(Executor.java:231)
Caused by: 
hudson.remoting.RequestAbortedException:
 java.io.InvalidClassException: [Ljava.lang.StackTraceElement;; serializable 
and externalizable flags conflict
at 
hudson.remoting.Request.abort(Request.java:299)
at 
hudson.remoting.Channel.terminate(Channel.java:782)
at 
hudson.slaves.Channels$1.terminate(Channels.java:77)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: 
java.io.InvalidClassException:
 [