I tried on a tomcat6 instance with the same exact setup and it worked, so I'm going to migrate jenkins there. The thing is that I could build it using the command line, on that same server, so unless a hypothetic missing dependency is on the classpath it shouldnt build.
I could try to build a hello world project with maven on the Tomcat 5 instance to be sure that the issue is related to tomcat. Shouldnt the maven exception give some kind of clue as to what class could not be loaded? Le 9 nov. 2012 00:07, "Varghese Renny" <[email protected]> a écrit : > Hi, > This error usually occur because of missing project dependencies that > you define on pom.xml. Like jar file missing or adding dependencies which > contain the class file it's looking for..You need to analyze it correctly.. > Another cause can be jvm is not able to load full class defenition..Try to > increase your jvm_opts for tomcat..In my machine it's location is > /etc/default/tomcat6..You can edit this file increase your heap size. > > Regards, > varghese > > > On Fri, Nov 9, 2012 at 3:11 AM, Remi Carton <[email protected]> wrote: > >> Hello, >> >> I am having trouble getting my maven job to work, even though it is a >> basic setup: >> - jenkins 1.489 (no slaves) on linux >> - tomcat 5.0 >> - jvm: 1.6.0_03-b05 >> - maven plugin 1.489 >> >> and this is for a maven 2.2.1 build. >> >> I tried installing Maven with both a manual install and the automated >> install (only once at a time). >> >> And then it's a basic maven job: cvs checkout and the maven goals "clean >> compile" >> >> What happens is the following: >> >> >> $ no changes detected >> Unpacking >> http://archive.apache.org/**dist/maven/binaries/apache-**maven-2.2.1-bin.zip >> <http://archive.apache.org/dist/maven/binaries/apache-maven-2.2.1-bin.zip> >> to /users/tomcat/.jenkins/tools/**Maven/Maven_2.2.1 on Jenkins >> Parsing POMs >> FATAL: >> org/codehaus/classworlds/**NoSuchRealmExceptionjava.lang.NoClassDefFoundError >> >> <http://stacktrace.jenkins-ci.org/search?query=java.lang.NoClassDefFoundError>**: >> org/codehaus/classworlds/**NoSuchRealmException >> at >> hudson.maven.**MavenEmbedderUtils.**buildPlexusContainer(**MavenEmbedderUtils.java:163) >> >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenEmbedderUtils.buildPlexusContainer&entity=method> >> at >> hudson.maven.**MavenEmbedderUtils.**buildPlexusContainer(**MavenEmbedderUtils.java:156) >> >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenEmbedderUtils.buildPlexusContainer&entity=method> >> at hudson.maven.MavenEmbedder.<**init>(MavenEmbedder.java:109) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenEmbedder.%3Cinit%3E&entity=method> >> at hudson.maven.MavenEmbedder.<**init>(MavenEmbedder.java:136) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenEmbedder.%3Cinit%3E&entity=method> >> >> >> >> I thought something was wrong with my maven install/maven_home, so I >> tried using a manually installed maven and setting the maven_home in >> jenkins, but exactly same result with the manual maven. >> If I check out my code on the server, I can run the build in the command >> line with that maven installation, everything runs fine. >> >> My guess is that there is something wrong with the environment used by >> jenkins for calling maven, did I miss a step in the settings? They seemed >> pretty straightforward and my usecase is as simple as it gets. Could it be >> the tomcat version? >> >> Sorry if this is a common or obvious issue, but I have been trying for a >> long time and even the venerable google could not help me troubleshoot this >> one. >> >> I'd be very thankful if someone could give me a little help on that one! >> > >
