Author: manik.surtani(a)jboss.com Date: 2010-04-20 13:02:26 -0400 (Tue, 20 Apr 2010) New Revision: 8386 Modified: core/trunk/README-Maven.txt Log: UPdated README Modified: core/trunk/README-Maven.txt =================================================================== --- core/trunk/README-Maven.txt 2010-04-20 16:53:23 UTC (rev 8385) +++ core/trunk/README-Maven.txt 2010-04-20 17:02:26 UTC (rev 8386) @@ -50,10 +50,10 @@ coverage reports using EMMA. -1.2. Setting up your WebDAV username and password to deploy project snapshots ------------------------------------------------------------------------------ +1.2. Setting up your username and password to make releases and shapshot release +-------------------------------------------------------------------------------- -You will also have to configure maven to use your username and password to access this repository. For this, you will +You will also have to configure maven to use your username and password to access the repository. For this, you will have to modify the servers section of maven settings file ($MAVEN_HOME/conf/settings.xml, or ~/.m2/settings.xml). Something similar to the following should be added: @@ -63,11 +63,22 @@ <servers> ... + <server> - <id>snapshots.jboss.org</id> - <username>webdav-user</username> - <password>webdav-pass</password> + <id>jboss-developer</id> + <username>jboss.org username</username> + <password>jboss.org password</password> </server> + <server> + <id>jboss-snapshots</id> + <username>jboss.org username</username> + <password>jboss.org password</password> + </server> + <server> + <id>jboss-releases</id> + <username>jboss.org username</username> + <password>jboss.org password</password> + </server> ... </servers> @@ -82,45 +93,12 @@ Very simple. Make sure you have the version number in your pom.xml set to a non-SNAPSHOT version. Maven will pick up on this and deploy to your release repository rather than the snapshot repository. -JBoss release repository cannot be accessed via WebDAV, as the snapshot repository can. So what you need to do is: +The JBoss repository will hold this release in a staging directory which can be accessed by logging in to -1) Check out the release repository from Subversion (svn co https://svn.jboss.org/repos/repository.jboss.org/maven2) -2) Add a property in ~/.m2/settings.xml to point to this 'local' copy of the repo. (See maven settings below) -3) Update your project's pom.xml to reflect a non-SNAPSHOT version number -4) Deploy your project (mvn clean deploy) -5) Check in your 'local' copy of the repo checked out in (1), adding any new directories/files created by (4). +https://repository.jboss.org/nexus -1.4. Maven settings.xml ------------------------ +After verifying the POM and the artifacts in Nexus, you can then close the repository and push the relase live. -Working with the JBoss Cache source tree, I have configured my ~/.m2/settings.xml to look like: - -<settings> - - <servers> - <server> - <id>snapshots.jboss.org</id> - <username>MY_JBOSS_ORG_USERNAME</username> - <password>WONT_TELL_YOU</password> - </server> - </servers> - - - <profiles> - <profile> - <id>jboss</id> - <properties> - <maven.repository.root>/Users/manik/Code/maven2</maven.repository.root> - </properties> - </profile> - </profiles> - - <activeProfiles> - <activeProfile>jboss</activeProfile> - </activeProfiles> - -</settings> - 2. TESTING ==========