[CONF] Apache Camel: Testing a release candidate (page edited)

[confluence]

Page Edited : CAMEL : Testing a release candidate Testing a release candidate has been edited by Gert Vanthienen (Jul 14, 2008). (View changes) Content: When a release candidate has been cut, a vote is started, inviting all members of the community to test the release candidate before actually declaring it an official release. What/how to test before casting your vote? Checking the distributables (tar.gz and/or zip files) Just download the distributables and check their contents: do they contain the appropriate source/class/jar files? do they contain the required legal files? do they have the correct MD5/SHA1 sum? Building the release candidate from source Download and unpack the release candidate's source distribution. To test if all dependencies are available and all the necessary Maven repositories have been properly declared, it's best to temporarily move aside (or delete) your local Maven repo: mv ~/.m2 ~/.m2.backup Afterwards, do a full build as usual, preferably including running all unit tests. Testing the binary distribution by running the examples Download and unpack the binary distribution. Try running the examples. If you skipped the previous step (Building the release candidate), you will have to specify the staging repo whenever you execute a mvn command for testing the examples mvn camel:run -DremoteRepo=http://people.apache.org/~hadrian/apache-camel-1.4.0-RC1/maven2

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences