1 Reply Latest reply on Jul 15, 2010 1:03 PM by Paul Gier

    The right way to use the staging servers

    Jay Balunas Master

      Hi Paul,

       

      Nick and I were just discussing options for the correct way to use the staging servers for testing. 

       

      From this discussion - Some artifacts cannot be downloaded from staging repository I know that there is issue with setting stage repo in settings.xml.  That is fine, although we may upgrade to Maven 3, we are not 100% on that yet.

       

      To work around this ( and to be honest even if it was working ) we were going to create two profiles ( in our parent for now ) "richfaces-stage" and "richfaces-clean-stage".  "richfaces-stage" will use https://repository.jboss.org/nexus/content/repositories/staging/ while "richfaces-clean-stage" will use https://repository.jboss.org/nexus/content/repositories/jboss_release_staging_profile-XXX where XXX is the private stage.  That profile would require a property passed in to set that.

       

      Note that both of these approached require mirror setting in settings.xml for these report-ids.

       

      Are these good approached to using the stage sever?  Could these be added to jboss-parent?

       

      Either way - I thing that http://community.jboss.org/wiki/MavenDeployingaRelease needs more details ( or its own page ) on using the stage server.  Any advice would be appreciated.

       

      Also Seam/Weld use the nexus plugin - http://seamframework.org/Seam3/ModuleReleaseProcedure#H-DrivingTheReleaseWithMaven Is this something that we can use with our nexus, could we have a page that describes this if it is useful.

       

      Thanks,

      Jay

        • 1. Re: The right way to use the staging servers
          Paul Gier Master

          I recommend using a custom settings.xml file to define the staging repository.  The custom settings can also point to a local repository that is specific to the test build you are running.  This will ensure that you don't pollute the system-wide local Maven repo, and ensure that you are testing from a clean repo.

           

          You can use the specific staging repo URL in your settings.xml, or you can use a group URL which includes all the staging repos:

           

          https://repository.jboss.org/nexus/content/groups/staging/
          

           

          Regarding the nexus maven plugin, you can use that if you like.  There is documentation on the sonatype site:

          http://plugins.sonatype.org/nexus-maven-plugin/