Maven Repository Test Results

Version 25

    This page tracks the results and notes for each tester.  A success or failure should be noted for each test.  Each failure should be documented with a failure page that follows the template: Maven Repository Test Results - Failure Report.   A link to the failure report should be added under the testers name and under the appropriate test section.

     

     

    Paul Gier

     

     

    Lincoln Baxter

     

    1. Maven Repository Test Plan - User Authentication - PASSED

    2. Maven Repository Test Plan - Consuming Repo Artifacts - PASSED (with warnings)

     

    Downloading: https://jbtest.sonatype.org/content/groups/public/org/apache/maven/plugins/maven-plugins/13/maven-plugins-13.pom
    11K downloaded  (maven-plugins-13.pom)
    [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'bb4f5f7151104ffe6f4d303276c030c69aca669c'; remote = 'dfbacfc6302d31460cee3a60f1805cb51fff8fe9' - RETRYING
    Downloading: https://jbtest.sonatype.org/content/groups/public/org/apache/maven/plugins/maven-plugins/13/maven-plugins-13.pom
    11K downloaded  (maven-plugins-13.pom)
    [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'bb4f5f7151104ffe6f4d303276c030c69aca669c'; remote = 'dfbacfc6302d31460cee3a60f1805cb51fff8fe9' - IGNORING

     

    Downloading: https://jbtest.sonatype.org/content/groups/public/com/thoughtworks/xstream/xstream/1.3.1/xstream-1.3.1.pom
    11K downloaded  (xstream-1.3.1.pom)
    [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'd0965debefdcd42ec3de04a44e2b6e6ca93360d9'; remote = '<html>
    <head><title>400' - RETRYING
    Downloading: https://jbtest.sonatype.org/content/groups/public/com/thoughtworks/xstream/xstream/1.3.1/xstream-1.3.1.pom
    11K downloaded  (xstream-1.3.1.pom)
    [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'd0965debefdcd42ec3de04a44e2b6e6ca93360d9'; remote = '<html>
    <head><title>400' - IGNORING

     

    3. Maven Repository Test Plan - Save Proxied Artifacts - PASSED

    4. Maven Repository Test Plan - Searching for Artifacts - PASSED

    5. Maven Repository Test Plan - Deploying Snapshot Artifacts - PASSED

    6. Maven Repository Test Plan - Deploying Release Artifacts - PASSED

     

     

     

    David Vrzalik

     

    1. Maven Repository Test Plan - User Authentication - PASSED

         I was able to log in using my credentials. As Hardy pointed out, user managed repositories disappeared. Is this a feature?

     

    2. Maven Repository Test Plan - Consuming Repo Artifacts - PASSED

         I built several demo projects using the testing repo (...jbossas/projects/demos/microcontainer, ...microcontainer/mcdocs/examples/User_Guide), all builds went fine.

     

    3. Maven Repository Test Plan - Save Proxied Artifacts - PASSED

         3rd party dependency was downloaded and stored.

     

    4. Maven Repository Test Plan - Searching for Artifacts - PASSED

         All artifacts found.

     

    5. Maven Repository Test Plan - Deploying Snapshot Artifacts - PASSED

         Snapshot of a demo application was sucesfully deployed.

     

    6. Maven Repository Test Plan - Deploying Release Artifacts - PASSED

         Non-snapshot version was succesfully deployed in the staging repository and then promoted.


    Andrew Lee Rubinger

    Step 1: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-TestConfiguration

     

    Build using new settings SUCCESS
    mvn clean install -s /home/alr/.m2/settings-jbtest.xml

     

    Deploy SNAPSHOT using new settings SUCCESS
    mvn deploy -s ~/.m2/settings-jbtest.xml -DaltDeploymentRepository=jbtest::default::https://jbtest.sonatype.org/content/repositories/snapshots/

    Step 2: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-UserAuthentication

     

    Can now see the repositories after login.

    Step 3: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-ConsumingRepoArtifacts

     

    For instance the artifacts came from the right source:

    Downloading: https://jbtest.sonatype.org/content/groups/public/org/glassfish/common/glassfish-api/3.0.1-b02/glassfish-api-3.0.1-b02.jar

    Step 4: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-SaveProxiedArtifacts

     

    Observed that JUnit 4.7 has been cached in storage from Maven Central

    Step 5: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-SearchingforArtifacts

     

    Search for org.glassfish.extras returned expected results from the Source Index: "GlassFish (Cache)"

    Step 6: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-DeployingSnapshotArtifacts

     

    I can see org.jboss.shrinkwrap:*:1.0.0-SNAPSHOT deployed into https://jbtest.sonatype.org/content/repositories/snapshots/ from the Repo Manager UI.

    Step 7: SUCCESS

    http://community.jboss.org/wiki/MavenRepositoryTestPlan-DeployingReleaseArtifacts

     

    I could deploy to the staging repo and promote the release, seeing 1.0.0-alpha-6 of ShrinkWrap in the releases

     

    Randall Hauch

    1. Maven Repository Test Plan - User Authentication - PASSED using the username/password combination defined in Paul's email.  I was able to see the "Staging" repository in the left-hand pane under the "Enterprise" group, select that repository and browse its contents.

    2. Maven Repository Test Plan - Consuming Repo Artifacts - PASSED. Per the test, I used a new local repository and was able to perform a clean of the ModeShape trunk. All artifacts were downloaded from http://jbtest.sonatype.org/content/groups/public/, which is the URL of the mirror in my Maven settings file. I also updated my Eclipse settings to use the jbtest-settings.xml file, and this build also worked successfully.

    3. Maven Repository Test Plan - Save Proxied Artifacts - PASSED. Before running my build, I verified using the Nexus Repository web interface that several of ModeShape's 3rd party dependencies were not already in the "Public Repositories" group (http://jbtest.sonatype.org/content/groups/public/). Then after my build downloaded these 3rd party libraries (via http://jbtest.sonatype.org/content/groups/public/ URLs), I verified using the Nexus Repository web interface that these 3rd party artifacts were indeed downloaded and cached in the repository. I was also able to view artifact metadata (per http://www.sonatype.com/books/nexus-book/reference/using-sect-browsing.html#using-sect-viewing-metadata). I noticed that the repository contained none of the source JARs for my 3rd party dependencies, so I used Eclipse to download the sources (could have also done this via the command line) and verified that the repository now contained the source JARs for at least some of ModeShape's 3rd party dependencies.

    4. Maven Repository Test Plan - Searching for Artifacts - PASSED. Searched for a number of classes within JBoss DNA (as the ModeShape 1.0.0.Beta1 release was not yet loaded into Nexus), and all were found in the correct artifact (including those with a 'tests' classifier). I did notice, however, that 'source' artifacts were not searched, and there's no way to view a source file for a class even when the source artifact is stored in the repository.

    5. Maven Repository Test Plan - Deploying Snapshot Artifacts - FAILED. Ran the command to deploy to the SNAPSHOT repository, but got a 413 return code during the uploading of an artifact.  For details, see Maven Repository Test Results - Deploy Snapshot Failure

    6. Maven Repository Test Plan - Deploying Release Artifacts - NOT ATTEMPTED. The same error for #5 would likely happen.

     

    Note on performance. The first time I ran my build, I had a clean local repository and Nexus had not yet loaded many of ModeShape's 3rd party dependencies.  Yet even in this case, my complete build ran in about 00:13:37, which is significantly faster than the 25+ minutes it previously took during my last release. I then cleaned out my local repository again, and this time my build ran in about 00:09:49. As expected, this was a bit faster than before, since Nexus had the artifacts cached. Very nice improvement!

     

    Hardy Ferentschik

    1. Maven Repository Test Plan - User Authentication - FAILED

    I used my JBoss credentials. No problem with logging in. I was able to see the Staging repository in the left-hand pane under the "Enterprise" group, select that repository and browse its contents. Added some comments regarding what to actually expect in the repository list to the test plan.

    I had problems though to view the User Managed Repositories when being logged in though. Without logging in, I can see the user managed repositories:

    nexus-public.png

    After logging in these repostitories disappear:

    nexus-logged-in.png

     

    2. Maven Repository Test Plan - Consuming Repo Artifacts - FAILED. Trying to buid Hibernate Validator failed. It worked yesterday (02.02.10), but today the build fails:

     

    523$ mvn clean install -s ~/.m2/settings-jbtest.xml
    [INFO] Scanning for projects...
    [INFO] Reactor build order: 
    [INFO]   Hibernate Validator Parent
    [INFO]   Hibernate Validator
    [INFO]   Hibernate Validator Quickstart
    [INFO]   Hibernate Validator Legacy
    [INFO]   Hibernate Validator TCK Runner
    [INFO]   Hibernate Validator Annotation Processor
    Downloading: http://jbtest.sonatype.org/content/groups/public/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.pom
    [INFO] Unable to find resource 'org.apache.maven.wagon:wagon-webdav:pom:1.0-beta-2' in repository central (http://repo1.maven.org/maven2)
    Downloading: http://jbtest.sonatype.org/content/groups/public/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom
    [INFO] Unable to find resource 'org.codehaus.plexus:plexus-utils:pom:1.1' in repository central (http://repo1.maven.org/maven2)
    Downloading: http://jbtest.sonatype.org/content/groups/public/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
    Downloading: http://jbtest.sonatype.org/content/groups/public/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar
    [INFO] Unable to find resource 'org.codehaus.plexus:plexus-utils:jar:1.1' in repository central (http://repo1.maven.org/maven2)
    [INFO] Unable to find resource 'org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2' in repository central (http://repo1.maven.org/maven2)
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.
    
    
    
    Missing:
    ----------
    1) org.codehaus.plexus:plexus-utils:jar:1.1
      Try downloading the file manually from the project website.
    
      Then, install it using the command: 
          mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
    
      Alternatively, if you host your own repository you can deploy the file there: 
          mvn deploy:deploy-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
    
      Path to dependency: 
          1) org.hibernate:hibernate-validator-parent:pom:4.1.0-SNAPSHOT
          2) org.codehaus.plexus:plexus-utils:jar:1.1
    
    2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
    
      Try downloading the file manually from the project website.
    
      Then, install it using the command: 
          mvn install:install-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-webdav -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file
    
      Alternatively, if you host your own repository you can deploy the file there: 
          mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-webdav -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
    
      Path to dependency: 
          1) org.hibernate:hibernate-validator-parent:pom:4.1.0-SNAPSHOT
          2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2
    
    ----------
    2 required artifacts are missing.
    
    for artifact: 
      org.hibernate:hibernate-validator-parent:pom:4.1.0-SNAPSHOT
    
    from the specified remote repositories:
      jbtest-releases (http://jbtest.sonatype.org/content/groups/public)
    
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 2 seconds
    [INFO] Finished at: Wed Feb 03 11:50:08 GMT-04:00 2010
    [INFO] Final Memory: 4M/80M
    [INFO] ------------------------------------------------------------------------
    
    

     

    Funny enough doing a GAV search via the web interface seems to indicate that for example org.codehaus.plexus:plexus-utils:jar:1.1 should be in the repo:

    nexus-search-results.png

    -----

    Turns out the problem was a missing re-direct. The access to the repo should be via https. Configuration changes are being made

    -----

    After switching to https I was able to build Hiberante Core, Search, Validator and Meta Model Generator using the test proxy. All artifacts came from proxy.

     

    3. Maven Repository Test Plan - Save Proxied Artifacts - FAILED

    I think the artifacts are saved and cached, but I cannot confirm it, because I cannot see the user managed repostitories when logged in. See screenshot above.

     

    4. Maven Repository Test Plan - Searching for Artifacts - PASSED (initial failure).

    Searched for several classes in hibernate-jpa-2.0-api. However my inital search for IdClass (also the first search against any class in hibernate-jpa-2.0-api) failed with the following error message.

    failed-search.png

    After that I searched for the with the full class name javax.persistence.IdClass and it worked. I was then also able to search just IdClass or MapsId.

     

    5. Maven Repository Test Plan - Deploying Snapshot Artifacts - PASSED

    I tried mvn deploy -s ~/.m2/settings-jbtest.xml -DaltDeploymentRepository=jbtest::default::https://jbtest.sonatype.org/content/repositories/snapshots/ and mvn deploy -s ~/.m2/settings-jbtest.xml (in this case I changed the distributionManagement in the pom). There was a difference in the result though. In the first case the deployed snapshot contained still the name SNAPSHOT whereas in the latter approach (editing the pom) the SNAPSHOT string got properly replaced with a timestamp. Not sure if this is expected or not. Also I could only browse the snapshot repo when not logged in.

     

    6. Maven Repository Test Plan - Deploying Release Artifacts - PASSED

    Followed the steps in the test plans and everything worked. When I searched after promoting the artifact I noticed that it appeared in the release repo, but was also still in the staging repo as well. Is this intended?

     

    Artifacts still seems to be in te staging repo hours later

    search.png

     

     

    Tom Jenkinson

    Test Configuration

    Passed

    Test User Authentication

    Passed

    Test Consuming Repo Artifacts

    Passed

    Downloading: https://jbtest.sonatype.org/content/groups/public/org/jboss/jbossas/jboss-as-component-matrix/5.1.0.GA/jboss-as-component-matrix-5.1.0.GA.pom

    Test Save Proxied Artifacts

    Passed

    org/codehaus/stomp/stompconnect Was present

    Test Searching for Artifacts

    Passed

    Searched for: org/codehaus/stomp/stompconnect before and after the save proxy artifacts test

    Test Deploying Snapshot Artifacts

    Passed

    Had to edit distributionManagement section of pom.xml as our artifacts are not in any maven repo yet
    Still used the following command:
    mvn deploy -s ~/.m2/settings-jbtest.xml -DaltDeploymentRepository=jbtest::default::https://jbtest.sonatype.org/content/repositories/snapshots/

    Test Deploying Release Artifacts

    Passed
    Found a copy in staging and release same result as "Hardy Ferentschik"
    Had to edit distributionManagement section of pom.xml as our artifacts are not in any maven repo yet
    mvn deploy -s ~/.m2/settings-jbtest.xml -DaltDeploymentRepository=jbtest::default::https://jbtest.sonatype.org/service/local/staging/deploy/maven2/