Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-8968

Fix Tomcat deployment

    XMLWordPrintable

    Details

      Description

      Using standard "lightweight" wagon, big files deployment fails:

      Uploading: http://maven.in.nuxeo.com/nexus/content/repositories/public-snapshots/org/nuxeo/ecm/distribution/nuxeo-distribution-tomcat/5.6-SNAPSHOT/nuxeo-distribution-tomcat-5.6-20120301.135716-21-nuxeo-cap-sdk.zip
      [INFO] ------------------------------------------------------------------------
      [ERROR] FATAL ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] Java heap space
      [INFO] ------------------------------------------------------------------------
      [INFO] Trace
      java.lang.OutOfMemoryError: Java heap space
      	at java.util.Arrays.copyOf(Arrays.java:2786)
      	at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
      	at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
      	at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:492)
      	at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:457)
      	at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:411)
      	at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
      	at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
      	at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
      	at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
      	at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
      	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
      	at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:184)
      	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
      	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
      	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
      	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
      	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
      	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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
      	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
      	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
      	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

      Using alternate "httpclient" wagon generates wrong checksums (which is a blocker issue for proxying artifacts).
      Use of pre-emptive basic auth doesn't fix it in Maven 2.2.1.

      mvn deploy -Dmaven.wagon.provider.http=httpclient -Dhttp.authentication.preemptive=%b,true

      => issues WAGON-277, WAGON-284, WAGON-304, NEXUS-4347, ...

      Use of org.apache.maven.wagon:wagon-http:2.0 should have fixed the checksums issue but I couldn't validate it.

      It seems using the dav protocol is a viable workaround.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: