You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Deploying snapshots

There is no need to manually deploy snapshots.
Snapshots are automatically deployed by Hudson build job to the Nexus snapshot repository at https://repository.apache.org/content/repositories/snapshots/org/apache/wink

Performing a release

For the most part, we follow the same instructions that the maven team uses. http://maven.apache.org/developers/release/releasing.html

Basically, setup your settings.xml file as they described.

After that is setup, you need to update the release_notes.txt in the src/doc, and run the below commands.

mvn release:prepare 
mvn release:perform -P CIBuild

Notice: CIBuild profile is responsible to generate javadocs and build Wink sources/binaries archives.
JIRA http://jira.codehaus.org/browse/MRELEASE-459 prevents us from setting this profile inside maven-release-plugin configuration. The workaround is to path this profile as command line parameter.

                  <plugin>
                    <artifactId>maven-release-plugin</artifactId>
                    <configuration>
                      <tagBase>https://svn.apache.org/repos/asf/incubator/wink/tags</tagBase>
                      <preparationGoals>clean install</preparationGoals>
                      <autoVersionSubmodules>true</autoVersionSubmodules>
                      <!-- Run  CIBuild profile from command line for release:perform-->
                      <!-- mvn release:perform -P CIBuild-->
                      <!-- http://jira.codehaus.org/browse/MRELEASE-459 -->
                      <!-- releaseProfiles>CIBuild</releaseProfiles-->
                    </configuration>
                </plugin>

That will tag the release, update the poms, etc... Then build it (off the tag) and deploy everything (including source jars and javadoc jars) to the Nexus repository location and gpg signs everything. When the build is done staging, you need to login to the Nexus repository and "close" the staging are. See the Maven page above for instructions. That is very important. After the staging are is closed, note the URL for the staging area as you will need that for the vote.

At this point, everything "pre-vote" is done. Call the vote.

After the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well. See above Maven team release page.

Also, don't forget to copy the actual distributions to people.apache.org:/www/www.apache.org/dist/cxf.

Unpack the javadocs. Create a new directory in /www/cxf.apache.org/javadoc to match the version number and then unpack the cxf-bundle/$version/*-javadoc.jar from the maven repo into that new directory. Update the Navigation page in confluence to point to the new javadoc dir.

Finally, update the download pages and the news page.

  • No labels