Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.10.0
    • Fix Version/s: None
    • Component/s: Maven Embedder
    • Labels:
      None
    • Environment:
    • Global Rank:
      957

      Description

      When running (using a launcher) a deploy on my remote nexus with the new 0.10.0 m2e using embedded maven3, I now get a transfer fail (400).

      This was working with the:

      • 0.9.9-dev build (using the maven embed)
      • 0.10.0 using a default external maven (2.1.0)
      • command line maven-3 alpha 6

      When looking The basic authentication credentials (ftardif) seems not to be correctly passed on the PUT:

      142.120.93.34 - - [15/Feb/2010:15:11:42 -0500] "GET /devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/maven-metadata.xml HTTP/1.1" 401 472
      142.120.93.34 - ftardif [15/Feb/2010:15:11:42 -0500] "GET /devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/maven-metadata.xml HTTP/1.1" 200 375
      142.120.93.34 - ftardif [15/Feb/2010:15:11:42 -0500] "GET /devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/maven-metadata.xml.sha1 HTTP/1.1" 200 40
      142.120.93.34 - - [15/Feb/2010:15:11:42 -0500] "PUT /devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.201145-14.jar HTTP/1.1" 401 472
      142.120.93.34 - ftardif [15/Feb/2010:15:11:42 -0500] "PUT /devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.201145-14.jar HTTP/1.1" 400 294

      And here's the debug output for the deploy execution:

      [INFO] — maven-deploy-plugin:2.4:deploy (default-deploy) @ callcontrol-gear —
      [DEBUG] Created new class realm plugin>org.apache.maven.plugins:maven-deploy-plugin:2.4
      [DEBUG] Populating class realm plugin>org.apache.maven.plugins:maven-deploy-plugin:2.4
      [DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.4
      [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.1
      [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6
      [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
      [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
      [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.6
      [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
      [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' with basic configurator -->
      [DEBUG] (f) artifact = com.bell.cts.callgears:callcontrol-gear:jar:1.2.3-SNAPSHOT
      [DEBUG] (f) attachedArtifacts = [com.bell.cts.callgears:callcontrol-gear:java-source:sources:1.2.3-SNAPSHOT]
      [DEBUG] (f) deploymentRepository = id: nexus
      url: https://shrek/devel/nexus/content/repositories/snapshots
      layout: default
      snapshots: [enabled => true, update => daily]
      releases: [enabled => true, update => daily]

      [DEBUG] (s) localRepository = id: local
      url: file:///D:/m2/repository/
      layout: none

      [DEBUG] (f) packaging = jar
      [DEBUG] (f) pomFile = D:\devel\workspace\callcontrol-gear\pom.xml
      [DEBUG] (f) skip = false
      [DEBUG] (f) updateReleaseInfo = false
      [DEBUG] – end configuration –
      [INFO] Retrieving previous build number from nexus
      [DEBUG] Reading resolution-state from: D:\m2\repository\com\bell\cts\callgears\callcontrol-gear\1.2.3-SNAPSHOT\resolver-status.properties
      [DEBUG] Writing resolution-state to: D:\m2\repository\com\bell\cts\callgears\callcontrol-gear\1.2.3-SNAPSHOT\resolver-status.properties
      Uploading: https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 2:23.203s
      [INFO] Finished at: Mon Feb 15 15:02:50 EST 2010
      [INFO] Final Memory: 6M/43M
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on project callcontrol-gear: Error deploying artifact: Transfer failed: [400] https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar -> [Help 1]
      org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on project callcontrol-gear: Error deploying artifact: Transfer failed: [400] https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:585)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:324)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
      at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
      at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
      at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
      Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying artifact: Transfer failed: [400] https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar
      at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:195)
      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:577)
      ... 14 more
      Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Transfer failed: [400] https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar
      at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:92)
      at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
      ... 16 more
      Caused by: org.apache.maven.wagon.TransferFailedException: Transfer failed: [400] https://shrek/devel/nexus/content/repositories/snapshots/com/bell/cts/callgears/callcontrol-gear/1.2.3-SNAPSHOT/callcontrol-gear-1.2.3-20100215.200250-13.jar
      at org.apache.maven.wagon.providers.http.JettyClientHttpWagon.put(JettyClientHttpWagon.java:563)
      at org.apache.maven.wagon.providers.http.JettyClientHttpWagon.put(JettyClientHttpWagon.java:481)
      at org.apache.maven.repository.legacy.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:498)
      at org.apache.maven.repository.legacy.DefaultWagonManager.putArtifact(DefaultWagonManager.java:450)
      at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:82)
      ... 17 more

        Activity

        Hide
        Fred Bricon added a comment -

        I confirm upgrading to async-http-client 1.4.0 fixes the 401 unauthorized issue.
        Couldn't get the update-dependencies profiles to correctly update the jars, so I manually added AHC 1.4.0 to the embedder plugin in m2eclipse-core rb-0.12.x branch.
        I can build my own m2eclipse-core distro, so I'm not in a hurry, but if it starts to be pressing for some people AND if you ever decide to make a 0.12.1 version (I know it's not planned), the attached patch will work.

        regards,

        Fred Bricon

        Show
        Fred Bricon added a comment - I confirm upgrading to async-http-client 1.4.0 fixes the 401 unauthorized issue. Couldn't get the update-dependencies profiles to correctly update the jars, so I manually added AHC 1.4.0 to the embedder plugin in m2eclipse-core rb-0.12.x branch. I can build my own m2eclipse-core distro, so I'm not in a hurry, but if it starts to be pressing for some people AND if you ever decide to make a 0.12.1 version (I know it's not planned), the attached patch will work. regards, Fred Bricon
        Hide
        Nicole Monit added a comment -

        Any progress on this issue? I have updated my M2Eclipse and now this is really annoying. as I understood, all you need to do is to change the Version of async-http-client to 1.4.0 in org.maven.ide.eclipse.maven_embedder/pom.xml

        Show
        Nicole Monit added a comment - Any progress on this issue? I have updated my M2Eclipse and now this is really annoying. as I understood, all you need to do is to change the Version of async-http-client to 1.4.0 in org.maven.ide.eclipse.maven_embedder/pom.xml
        Hide
        Pascal Rapicault added a comment -

        On Friday Igor announced a new stage build of m2e to address these issues. Could you please try it https://repository.sonatype.org/content/sites/forge-sites/m2e/0.12.1/N/0.12.1.201101071126/

        Show
        Pascal Rapicault added a comment - On Friday Igor announced a new stage build of m2e to address these issues. Could you please try it https://repository.sonatype.org/content/sites/forge-sites/m2e/0.12.1/N/0.12.1.201101071126/
        Hide
        Fred Bricon added a comment -

        0.12.1 works for me

        Show
        Fred Bricon added a comment - 0.12.1 works for me
        Hide
        Helene Bourassa added a comment -

        We continue to have this problem. Here are my test configurations against a Nexus Pro 1.9.1.1 in non-anonymous/https modes

        • Eclipse 3.6.2 with
        • m2eclipse 0.12.1.20110112-1712
        • m2eclipse 0.13.0.201105260005
        • m2eclipse 1.0.0.20110607-2117
        • Eclipse 3.5.2 with
        • m2eclipse 0.10.0.20100209-0800
        • external maven 2.2.1
        • login credentials obfuscated in settings.xml

        In all various m2eclipse, I've found the following.

        • M2eclipse does successfully download all of the required jars and dependencies for its own functionality (e.g. \org\apache\maven\plugins\maven-jar-plugin\2.2\maven-jar-plugin-2.2.jar)
        • M2eclipse does not download any of the project required dependencies. It seems to disregard the security credentials specified in settings.xml and attemtps to download artifacts anonymously which our corporate Nexus rejects if anonymous access is disabled.

        Pierre Awaragi

        Show
        Helene Bourassa added a comment - We continue to have this problem. Here are my test configurations against a Nexus Pro 1.9.1.1 in non-anonymous/https modes Eclipse 3.6.2 with m2eclipse 0.12.1.20110112-1712 m2eclipse 0.13.0.201105260005 m2eclipse 1.0.0.20110607-2117 Eclipse 3.5.2 with m2eclipse 0.10.0.20100209-0800 external maven 2.2.1 login credentials obfuscated in settings.xml In all various m2eclipse, I've found the following. M2eclipse does successfully download all of the required jars and dependencies for its own functionality (e.g. \org\apache\maven\plugins\maven-jar-plugin\2.2\maven-jar-plugin-2.2.jar) M2eclipse does not download any of the project required dependencies. It seems to disregard the security credentials specified in settings.xml and attemtps to download artifacts anonymously which our corporate Nexus rejects if anonymous access is disabled. Pierre Awaragi

          People

          • Assignee:
            Unassigned
            Reporter:
            Frederic Tardif
            Last Updated By:
            Helene Bourassa
          • Votes:
            11 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

            • Created:
              Updated:
              Date of First Response: