Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Problem with pushing to Maven

    Scheduled Pinned Locked Moved Support
    progetjava
    6 Posts 1 Posters 109 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Hello,

      A coworker of mine is attempting to use a Maven feed, and is having issues pushing to it. The following is a log of how he was attempting to use the feed, and the results. Is there something missing? What would need to change to get this to work?

      Thanks,
      Erick

      1. Configuration
        tested on:
        OS X 10.10

         javac -version
     javac 1.8.0_20

 mvn --version
     Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T09:29:23-08:00)
     Maven home: /usr/local/Cellar/maven/3.2.5/libexec
     Java version: 1.6.0_65, vendor: Apple Inc.
     Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
     Default locale: en_US, platform encoding: MacRoman
     OS name: "mac os x", version: "10.10", arch: "x86_64", family: "mac"

        this page:

         http://proget/maven-feeds/allenai-pipeline

        reports API endpoint:

         http://proget/maven2/allenai-pipeline

      2. Steps to reproduce

      2.1) Obtain junit source:

      git clone git@github.com:junit-team/junit.git
cd junit
git checkout 00911b1

      2.2) Edit as follows:
      +++ b/pom.xml
      @@ -84,16 +84,13 @@
      </ciManagement>
      <distributionManagement>
      <downloadUrl>https://github.com/junit-team/junit/wiki/Download-and-Install</downloadUrl>
      - <snapshotRepository>
      - <id>junit-snapshot-repo</id>
      - <name>Nexus Snapshot Repository</name>
      - <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
      - </snapshotRepository>
      - <repository>
      - <id>junit-releases-repo</id>
      - <name>Nexus Release Repository</name>
      - <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>
      - </repository>
      +
      +<snapshotRepository>
      + <id>deployment</id>
      + <name>Internal Releases</name>
      + <url>http://proget/maven2/allenai-pipeline</url>
      +</snapshotRepository>
      +
      <site>
      <id>junit.github.io</id>
      <url>gitsite:git@github.com/junit-team/junit.git</url>
      @@ -447,26 +444,6 @@
      -->
      <build>
      <plugins>
      - <plugin>
      - <!--
      - The goal is to sign all artifacts so that the user may verify them before downloading.
      - The automatic build system may reuire your key ID, and passphrase specified using system properties:
      - -Dgpg.passphrase="<passphrase>" -Dgpg.keyname="<your key ID>"
      - In order to create the key pair, use the command "gpg ––gen-key".
      - (–– stands for double dash)
      - -->
      - <artifactId>maven-gpg-plugin</artifactId>
      - <version>1.6</version>
      - <executions>
      - <execution>
      - <id>gpg-sign</id>
      - <phase>verify</phase>
      - <goals>
      - <goal>sign</goal>
      - </goals>
      - </execution>
      - </executions>
      - </plugin>
      </plugins>
      </build>
      </profile>

      2.3) publish

      mvn compile
# succeeds:

mvn release:prepare 
# mvn deploy, with debugging output:
mvn deploy -e -X

      1. results

        • expected result:

          published files

        • actual result:

          [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://proget/maven2/allenai-pipeline
          [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://proget/maven2/allenai-pipeline
          Downloading: http://proget/maven2/allenai-pipeline/junit/junit/4.13-SNAPSHOT/maven-metadata.xml
          [WARNING] Could not transfer metadata junit:junit:4.13-SNAPSHOT/maven-metadata.xml from/to deployment (http://proget/maven2/allenai-pipeline): Failed to transfer file: http://proget/maven2/allenai-pipeline/junit/junit/4.13-SNAPSHOT/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.
          org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata junit:junit:4.13-SNAPSHOT/maven-metadata.xml from/to deployment (http://proget/maven2/allenai-pipeline): Failed to transfer file: http://proget/maven2/allenai-pipeline/junit/junit/4.13-SNAPSHOT/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.
          at org.eclipse.aether.connector.basic.MetadataTransportListener.transferFailed(MetadataTransportListener.java:43)
          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
          at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
          at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:222)
          at org.eclipse.aether.internal.impl.DefaultDeployer.upload(DefaultDeployer.java:417)
          at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:290)
          at org.eclipse.aether.internal.impl.DefaultDeployer.deploy(DefaultDeployer.java:245)
          at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:413)
          at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:139)
          at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:171)
          at org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:250)
          at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
          at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
          at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
          at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
          at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
          at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
          at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
          at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
          at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
          at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
          at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
          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:289)
          at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
          at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
          at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
          Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://proget/maven2/allenai-pipeline/junit/junit/4.13-SNAPSHOT/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.
          at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1039)
          at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:977)
          at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
          at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
          at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
          at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)
          at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
          at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)
          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
          ... 32 more
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD FAILURE
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 18.793 s
          [INFO] Finished at: 2015-06-26T17:20:39-07:00
          [INFO] Final Memory: 11M/81M
          [INFO] ------------------------------------------------------------------------

      Product: ProGet
      Version: 3.6.1

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Thanks for the detailed bug report. We'll work on repro'ing this and get back to you soon. If all goes well we can have a fix available this week.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Has this been addressed? I'm having the same issue. I'm doing an initial deploy of an artifact to a proget server

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            Sorry for the delay- we should have a fix for this included in ProGet 3.8.0, which is scheduled for release tomorrow.

            1 Reply Last reply Reply Quote 0
            • ? This user is from outside of this forum
              Guest
              last edited by

              I run a Maven Feed on a local proget installation (Version 5.1.19 (Build 7)) and try to deploy a package with maven version 3.5.2.
              After the compilation of the package the upload starts and fails with this message.

              Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.jar (18 MB at 4.2 MB/s)
Uploading to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom
Progress (1): artifact-0.0.1.pom (1.7 kB)
Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom (1.7 kB at 6.5 kB/s)
Downloading from releases: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml
[WARNING] Could not transfer metadata test.package:artifact/maven-metadata.xml from/to releases (http://local-installation/maven2/maven-releases/): Failed to transfer file: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.

              The feed then contains the jar and pom file and the Event Log contains two Package Created Events.
              The Diagnostic Center shows the following error:

              Category:
Web

Message:
An error occurred processing a GET request to http://192.168.178.26/maven2/maven-releases/org/youth-alive/hello-world/maven-metadata.xml: Value cannot be null. Parameter name: version

Details: 
System.ArgumentNullException: Value cannot be null.
Parameter name: version
at Inedo.ProGet.Feeds.Maven.MavenVersion.Parse (System.String version) [0x00008] in <1349015ffbf342a689ae698d25b4ab7e>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.Maven.MavenFeedHandler.ProcessRequestAsync (System.Web.HttpContext context, Inedo.ProGet.Feeds.Maven.MavenFeed feed, System.String relativeUrl) [0x00190] in <dab0761184df4cae8729746ef4194b56>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler.ProcessRequestAsync (System.Web.HttpContext context) [0x000a4] in <dab0761184df4cae8729746ef4194b56>:0

              Is this really fixed?

              1 Reply Last reply Reply Quote 0
              • ? This user is from outside of this forum
                Guest
                last edited by

                Started new question.
                Please answer there. Thank you

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • 1 / 1
                • First post
                  Last post
                Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation