[JIRA] Closed: (HUDSON-4988) Maven 3 support in maven-plugin

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Closed: (HUDSON-4988) Maven 3 support in maven-plugin

Kohsuke Kawaguchi
Administrator

     [ http://issues.hudson-ci.org/browse/HUDSON-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

olamy closed HUDSON-4988.
-------------------------

    Resolution: Fixed

@unguiculus please do not reopen.
Your issue is traked by HUDSON-8390.
BTW you can fix your parent declaration if you don't wait the fix :-)

> Maven 3 support in maven-plugin
> -------------------------------
>
>                 Key: HUDSON-4988
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-4988
>             Project: Hudson
>          Issue Type: New Feature
>          Components: maven2
>            Reporter: zlosch
>            Assignee: olamy
>         Attachments: consoleText-maven3-site-build.zip, hudson-m3-tycho-debug-2.txt, hudson-m3-tycho-debug.log
>
>
> Hudson maven-plugin doesn't work with Maven 3 on Linux. On Linux Hudson builds its own Java command line and does some additional magic to launch Maven. On Windows it works fine because mvn.bat is used instead.
> The mechanism on Linux fails for two reasons:
> 1. classworlds-*.jar was upgraded to plexus-classworlds-2.2.2 with Maven 3, so the classpath is wrong.
> 2. plexus-classworlds-2.2.2 is not fully backward compatible. After renaming the jar to classworlds-2.2.2.jar the error is:
> $ /opt/java/x86_64/jdk1.6.0_16/bin/java -Xmx768m -XX:MaxPermSize=256m -cp /home/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.335.jar:/opt/maven/3.0-alpha-5/boot/classworlds-2.2.2.jar hudson.maven.agent.Main /opt/maven/3.0-alpha-5 /usr/share/tomcat5/webapps/hudson/WEB-INF/lib/remoting-1.335.jar /home/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.335.jar 32917
> Exception in thread "main" java.lang.NoSuchMethodError: org.codehaus.classworlds.Launcher.getWorld()Lorg/codehaus/classworlds/ClassWorld;
> at hudson.maven.agent.Main.main(Main.java:115)
> at hudson.maven.agent.Main.main(Main.java:62)
> ERROR: Failed to launch Maven. Exit code = 1
> Skipping sonar analysis due to bad build status FAILURE
> Finished: FAILURE
> Reason for the above error is that getWorld() returns a different type in 2.2.2 which isn't assignable to the type returned in 1.x.
> A general question: Why does Hudson use different mechanisms for launching Maven on Windows and Linux?
> Tested with 1.335

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira