This document is intended for committers who are packaging a release. It likely won't be of much use to anyone else.
If this is the first time you're doing a release you'll need to perform some setup.
<settings>
...
<servers>
<server>
<id>htmlunit-website</id>
<username>mguillem,htmlunit</username>
<!-- optional element:
<password>your-sourceforge-pwd</password>
-->
</server>
<server>
<id>sonatype-nexus-snapshots</id>
<username>your-jira-id</username>
<!-- optional element:
<password>your-jira-pwd</password>
-->
</server>
<server>
<id>sonatype-nexus-staging</id>
<username>your-jira-id</username>
<!-- optional element:
<password>your-jira-pwd</password>
-->
</server>
</servers>
...
</settings>For SnapShots:
<parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent>Now do this for each release:
mvn -up clean site package
mvn -Dmaven.test.skip=true org.apache.felix:maven-bundle-plugin:bundle
mvn scm:tag
mvn javadoc:jar mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging -DpomFile=pom.xml -Dfile=target/htmlunit-2.11.jar mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging -DpomFile=pom.xml -Dfile=target/htmlunit-2.11-sources.jar -Dclassifier=sources mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DrepositoryId=sonatype-nexus-staging -DpomFile=pom.xml -Dfile=target/htmlunit-2.11-javadoc.jar -Dclassifier=javadoc
ssh -t mguillem,htmlunit@shell.sf.net create
mvn -Dmaven.test.skip=true site:deploy