Tag the svn repository Now that the release is approved, it is time to tag the svn repo svn copy https: Sign and upload the artifacts It's now time to sign the release artifacts and upload them to a location accessible by other Apache commiters. Check out the branch svn co https: Prepare next release Update the file version. Move the page up in the TOC using the arrow button in the toolbar at the upper right, so that it's the first child page under the "Documentation" page.
|Date Added:||2 June 2010|
|File Size:||19.16 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If this is an incubator version, add the usual incubator disclaimer too. Introduction to Apache Ant.
It's time to update the download image used on the home page and the download page. For instance, to get the trunk version: We currently provide two options: Update also the download page with the new image and update the links to the download location.
You may need additional libraries to satisfy the build requirements of various packages installed using Apache Ant. Make sure you include some kind of disclaimer somewhere to inform people the release is not approved yet. This command creates a symlink from the configuration directory back to the installation directory as the package is expecting to find the files there. Then you can update the home page to refer to this image, and add a news item announcing the new version.
Making a release Requirements Requirements for making a release are similar to the requirements for building from source, except that sun jdk 1. This command does everything. Sometimes you may need to call ant clean-all if you have started to work with ant builds. Update the web site Add a link to the released version documentation in the web site. If you take the time to make the content of the release notes more "xooki compliant" by removing unnecessary end of lines and adding h2 h3 and h4 tagsthe page could then look like something like that: The Apache Ant package is a Java -based build tool.
Instead of a model where it is extended with apafhe commands, Ant is extended using Java classes. Short Descriptions ant is a Java based build tool used by many packages instead of the conventional make program.
Choose "Release Notes" as title, and "release-notes" as page id. Eclipse alone To develop with a simple eclipse install all you need is eclipse 3. To apzche so all you need is call the following ant target in your Ivy workspace: Launch the release script ant -Dbuild. If anything is wrong, fix and go back to step 4.
Apache Ant User Manual
Check that you have no pending modifications svn status If your working copy is clean, you can launch the release script. On the trunk, check that files which require update for apaxhe release are up to date. To do so, you need to: Verify the release Check that all zips can be opened correctly, and that running 'ant' after unzipping the source distribution works properly.
Modifications on the template files do not need to be merged, but if you apacje troubles during your release you may want to merge your fixes back to the trunk. Tag the svn repository Now alache the release is approved, it is time to tag the svn repo svn copy https: Prepare next release Update the file version. Double check the files which need to be updated for the release.
When you're done upload the content of the distrib directory to a publicly accessible web site, your apache personal site being a good location for this. Add release note page in the documentation. Move the page up in the TOC using the arrow button in the toolbar at the upper right, so that it's the first child page under the "Documentation" page.
You can also announce the release on popular web sites, like freshmeat. Then it will compile and run tests with coverage metrics. Merge your modifications back to the trunk if necessary.