• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      Create a Hudson job to build a maven2 project; enable Post-build Actions, "Deploy artifacts to Maven
      repository". The deployment does not publish the jar artifacts to the maven repository. The pom files
      are deployed but not the jar

      e-mail exchange with Kohsuke:

      > When using Hudson to create a Maven job to build and deploy artifacts. The deploy part does not
      publish the jar artifacts to the maven repository. It deploys the pom files but the jar files are not
      deployed.
      >
      > Please take a look at this job:
      > http://hudson.sfbay.sun.com/job/glassfish-v3-main-publisher/801/console

      Indeed. I'll take a look.

      > Note that this job is created using the "Build a maven2 project" option.
      >
      > Also, when using this option, the build is taking a LONG time. It took 7 hours to get this build to
      complete.
      > Is this a bug?

      It appears to be doing a lot of repetitive "archiving xyz" things. Again, let me take a look.

          [JENKINS-3256] maven job does not deploy jar artifacts

          objectify_smc added a comment -

          hudson.maven.reporters.MavenAggregatedArtifactRecord#deploy was only deploying the first MavenArtifactRecord of the build actions.

          The patch gets all MavenArtifactRecords from the build actions and deploys them in sequence.

          objectify_smc added a comment - hudson.maven.reporters.MavenAggregatedArtifactRecord#deploy was only deploying the first MavenArtifactRecord of the build actions. The patch gets all MavenArtifactRecords from the build actions and deploys them in sequence.

          xylo added a comment - - edited

          Same for me with the latest version of jenkins (1.614). Jenkins deloys the pom.xml, the sources.jar, and the javadoc.jar, but not the binary distribution (the actual jar file). I checked if all jar files are created and they are.

          In contrast to the original bug report I don't discover any LONG waiting time for the build. Everything (including the uploads to the maven repository) works quite fast on my machine. Thus it's not a timeout issue for me.

          xylo added a comment - - edited Same for me with the latest version of jenkins (1.614). Jenkins deloys the pom.xml, the sources.jar, and the javadoc.jar, but not the binary distribution (the actual jar file). I checked if all jar files are created and they are. In contrast to the original bug report I don't discover any LONG waiting time for the build. Everything (including the uploads to the maven repository) works quite fast on my machine. Thus it's not a timeout issue for me.

            kohsuke Kohsuke Kawaguchi
            janey janey
            Votes:
            5 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: