• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Platform: All, OS: All

      Using Maven 2.1.0.M1-RC17
      http://people.apache.org/~jdcasey/stage/current-maven-RC/ with Hudson fails due
      to not properly initialized instance of LifecycleExecutorInterceptor (for
      details please check the Maven user list
      http://www.nabble.com/Re%3A--PLEASE-TEST--Maven-2.0.10-RC11-p19207144.html ).

      The corresponding warning looks like these ones:

      [WARNING]

                            • WARNING ************

      This Maven runtime contains a LifecycleExecutor component with an incomplete
      configuration.

      LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
      Missing component requirement: org.apache.maven.project.MavenProjectBuilder

      NOTE: This seems to be a third-party Maven derivative you are using. If so,
      please notify the developers for this derivative project of the problem. The
      Apache Maven team is not responsible for maintaining the integrity of
      third-party component overrides.

      [WARNING]

                            • WARNING ************

      This Maven runtime contains a LifecycleExecutor component with an incomplete
      configuration.

      LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
      Missing component requirement:
      org.apache.maven.project.interpolation.ModelInterpolator

      NOTE: This seems to be a third-party Maven derivative you are using. If so,
      please notify the developers for this derivative project of the problem. The
      Apache Maven team is not responsible for maintaining the integrity of
      third-party component overrides.

      Cheers,
      Torsten

          [JENKINS-2373] Maven 2.1 Support

              • Issue 4023 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 4023 has been marked as a duplicate of this issue. ***

          steffeng added a comment -

          Maven 2.1 is not yet fully supported, as the interceptor is still compiled with
          an old interface version [1] that has changed with 2.1.

          I'm observing the second problem described in issue 3449 with hudson 1.323 and
          maven 2.2.1:
          java.lang.NoSuchMethodError:
          org.apache.maven.plugin.PluginManagerException.<init>(Ljava/lang/String;Ljava/lang/Exception;)V
          at
          hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:195)

          This code is run exceptional, but the exception to be chained in the executeMojo
          method is thrown by surefire (and is not too exotic) and swallowed completely.

          I looked at the packaged implementation of the PluginManagerInterceptor.
          This is still compiled with the old interface (decompiled code):

          /* 195*/ throw new PluginManagerException(e.getMessage(), e);
          [...]
          /* 195*/ // 45 87:invokespecial #21 <Method void
          PluginManagerException(String, Exception)>

          I could think of these options:

          • use reflection to instantiate the exception (strange but simple and does the
            trick for a while)
          • extract and overwrite the exception handling method (both jars must be modified)
          • compile the interceptor in two versions (no idea how to do that easily)
          • do something that is even cooler but fixes the problem

          [1]
          http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-core/src/main/java/org/apache/maven/plugin/PluginManagerException.java?r1=685450&r2=747855&diff_format=h

          steffeng added a comment - Maven 2.1 is not yet fully supported, as the interceptor is still compiled with an old interface version [1] that has changed with 2.1. I'm observing the second problem described in issue 3449 with hudson 1.323 and maven 2.2.1: java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManagerException.<init>(Ljava/lang/String;Ljava/lang/Exception;)V at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:195) This code is run exceptional, but the exception to be chained in the executeMojo method is thrown by surefire (and is not too exotic) and swallowed completely. I looked at the packaged implementation of the PluginManagerInterceptor. This is still compiled with the old interface (decompiled code): /* 195*/ throw new PluginManagerException(e.getMessage(), e); [...] /* 195*/ // 45 87:invokespecial #21 <Method void PluginManagerException(String, Exception)> I could think of these options: use reflection to instantiate the exception (strange but simple and does the trick for a while) extract and overwrite the exception handling method (both jars must be modified) compile the interceptor in two versions (no idea how to do that easily) do something that is even cooler but fixes the problem [1] http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-core/src/main/java/org/apache/maven/plugin/PluginManagerException.java?r1=685450&r2=747855&diff_format=h

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/hudson/main/maven-interceptor/src/main/java/hudson/maven/agent/PluginManagerInterceptor.java
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=22857
          Log:
          [FIXED JENKINS-2373] Fixed <tt>NoSuchMethodError</tt> error during error recovery with Maven 2.1. Will be in 1.330.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/main/maven-interceptor/src/main/java/hudson/maven/agent/PluginManagerInterceptor.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=22857 Log: [FIXED JENKINS-2373] Fixed <tt>NoSuchMethodError</tt> error during error recovery with Maven 2.1. Will be in 1.330.

          The underlying binary incompatible change is filed as http://jira.codehaus.org/browse/MNG-4550

          Kohsuke Kawaguchi added a comment - The underlying binary incompatible change is filed as http://jira.codehaus.org/browse/MNG-4550

          dsmiley added a comment -

          This is supposedly fixed I see but I'm still getting the triple-warnings taking up a half-page of my screen, starting each build. I'm using Hudson v1.372 and Maven 2.2.1

          dsmiley added a comment - This is supposedly fixed I see but I'm still getting the triple-warnings taking up a half-page of my screen, starting each build. I'm using Hudson v1.372 and Maven 2.2.1

          rdomingo added a comment -

          In build 1.378 my mvn 2.1 projects aren't build correctly, phase 'prepare-package' isn't executed and I get:

          [WARNING]

                                • WARNING ************

          This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

          LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
          Missing component requirement: org.apache.maven.project.MavenProjectBuilder

          NOTE: This seems to be a third-party Maven derivative you are using. If so, please
          notify the developers for this derivative project of the problem. The Apache Maven team is not
          responsible for maintaining the integrity of third-party component overrides.

          Should 'prepare-package' already work in hudson 1.378 ? Is there any workaround for this ?

          rdomingo added a comment - In build 1.378 my mvn 2.1 projects aren't build correctly, phase 'prepare-package' isn't executed and I get: [WARNING] WARNING ************ This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.MavenProjectBuilder NOTE: This seems to be a third-party Maven derivative you are using. If so, please notify the developers for this derivative project of the problem. The Apache Maven team is not responsible for maintaining the integrity of third-party component overrides. Should 'prepare-package' already work in hudson 1.378 ? Is there any workaround for this ?

          kiechu added a comment -

          I received the same warning (underneath) with Hudson 1.381 and Maven 2.2.1 on Ubuntu 10.04.1 LTS with both Sun Java6 JDK and Open Java 6 JDK.

          [bo-main-portlet] $ /usr/lib/jvm/java-6-sun/bin/java -cp /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.351.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2/ /opt/hudson/war/WEB-INF/lib/remoting-1.351.jar /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.351.jar 37014
          <===[HUDSON REMOTING CAPACITY]===>���channel started
          Executing Maven: -B -f /opt/hudson/work/jobs/bo-main-portlet-new/workspace/web/portlets/bo-main-portlet/pom.xml integration-test
          [WARNING]

                                • WARNING ************

          This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

          LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
          Missing component requirement: org.apache.maven.project.MavenProjectBuilder

          NOTE: This seems to be a third-party Maven derivative you are using. If so, please
          notify the developers for this derivative project of the problem. The Apache Maven team is not
          responsible for maintaining the integrity of third-party component overrides.

          [WARNING]

                                • WARNING ************

          This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

          LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
          Missing component requirement: org.apache.maven.project.interpolation.ModelInterpolator

          NOTE: This seems to be a third-party Maven derivative you are using. If so, please
          notify the developers for this derivative project of the problem. The Apache Maven team is not
          responsible for maintaining the integrity of third-party component overrides.

          [WARNING]

                                • WARNING ************

          This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

          LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
          Missing component requirement: org.apache.maven.ConfigurationInterpolator

          NOTE: This seems to be a third-party Maven derivative you are using. If so, please
          notify the developers for this derivative project of the problem. The Apache Maven team is not
          responsible for maintaining the integrity of third-party component overrides.

          kiechu added a comment - I received the same warning (underneath) with Hudson 1.381 and Maven 2.2.1 on Ubuntu 10.04.1 LTS with both Sun Java6 JDK and Open Java 6 JDK. [bo-main-portlet] $ /usr/lib/jvm/java-6-sun/bin/java -cp /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.351.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2/ /opt/hudson/war/WEB-INF/lib/remoting-1.351.jar /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.351.jar 37014 <=== [HUDSON REMOTING CAPACITY] ===>���channel started Executing Maven: -B -f /opt/hudson/work/jobs/bo-main-portlet-new/workspace/web/portlets/bo-main-portlet/pom.xml integration-test [WARNING] WARNING ************ This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.MavenProjectBuilder NOTE: This seems to be a third-party Maven derivative you are using. If so, please notify the developers for this derivative project of the problem. The Apache Maven team is not responsible for maintaining the integrity of third-party component overrides. [WARNING] WARNING ************ This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.interpolation.ModelInterpolator NOTE: This seems to be a third-party Maven derivative you are using. If so, please notify the developers for this derivative project of the problem. The Apache Maven team is not responsible for maintaining the integrity of third-party component overrides. [WARNING] WARNING ************ This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.ConfigurationInterpolator NOTE: This seems to be a third-party Maven derivative you are using. If so, please notify the developers for this derivative project of the problem. The Apache Maven team is not responsible for maintaining the integrity of third-party component overrides.

          lynggaard added a comment -

          I am wondering about this line you have pasted:

          "[bo-main-portlet] $ /usr/lib/jvm/java-6-sun/bin/java -cp /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.351.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2/ /opt/hudson/war/WEB-INF/lib/remoting-1.351.jar /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.351.jar 37014"

          My concern is that the maven-interceptor and remoting jar files have a much older version number than 1.381. I checked my hudson_home and in there the version numbers match my hudson version 1.382.

          How have you installed hudson and maven, and in which container do you run hudson ?

          lynggaard added a comment - I am wondering about this line you have pasted: " [bo-main-portlet] $ /usr/lib/jvm/java-6-sun/bin/java -cp /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.351.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2/ /opt/hudson/war/WEB-INF/lib/remoting-1.351.jar /opt/hudson/work/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.351.jar 37014" My concern is that the maven-interceptor and remoting jar files have a much older version number than 1.381. I checked my hudson_home and in there the version numbers match my hudson version 1.382. How have you installed hudson and maven, and in which container do you run hudson ?

          kutzi added a comment -

          No further info provided by reopener -> marking as Fixed again

          kutzi added a comment - No further info provided by reopener -> marking as Fixed again

          Victor Seva added a comment -

          system: Debian squeeze
          jenkins: 1.439 (deb package)
          tomcat: 6.0.28-9+squeeze1
          maven: 2.2.1-5
          openjdk-6-jdk: 6b18-1.8.9-0.1~squeeze1

          output:
          ---------------------------------------------------------------------------------------------------------------
          Parsing POMs
          [workspace] $ java -Xmx512m -XX:MaxPermSize=256m -Djava.util.prefs.systemRoot=~/.java -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.2.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.11.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.2.jar 37455
          <===[JENKINS REMOTING CAPACITY]===>channel started
          Executing Maven: -B -f /var/lib/jenkins/jobs/jboss_cervantesvirtual-gestor/workspace/pom.xml clean gwt:compile package -Dmaven.test.skip=true
          [WARNING]

                                • WARNING ************

          This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

          LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
          Missing component requirement: org.apache.maven.project.MavenProjectBuilder

          NOTE: This seems to be a third-party Maven derivative you are using. If so, please
          notify the developers for this derivative project of the problem. The Apache Maven team is not
          responsible for maintaining the integrity of third-party component overrides.
          ---------------------------------------------------------------------------------------------------------------

          Do you need more info?

          Victor Seva added a comment - system: Debian squeeze jenkins: 1.439 (deb package) tomcat: 6.0.28-9+squeeze1 maven: 2.2.1-5 openjdk-6-jdk: 6b18-1.8.9-0.1~squeeze1 output: --------------------------------------------------------------------------------------------------------------- Parsing POMs [workspace] $ java -Xmx512m -XX:MaxPermSize=256m -Djava.util.prefs.systemRoot=~/.java -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.2.jar:/usr/share/maven2/boot/classworlds.jar hudson.maven.agent.Main /usr/share/maven2 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.11.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.2.jar 37455 <=== [JENKINS REMOTING CAPACITY] ===>channel started Executing Maven: -B -f /var/lib/jenkins/jobs/jboss_cervantesvirtual-gestor/workspace/pom.xml clean gwt:compile package -Dmaven.test.skip=true [WARNING] WARNING ************ This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.MavenProjectBuilder NOTE: This seems to be a third-party Maven derivative you are using. If so, please notify the developers for this derivative project of the problem. The Apache Maven team is not responsible for maintaining the integrity of third-party component overrides. --------------------------------------------------------------------------------------------------------------- Do you need more info?

            Unassigned Unassigned
            tjuerge tjuerge
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: