Author: jaikiran Date: Thu May 2 13:53:36 2019 New Revision: 33884 Log: Fix the release notes for rc2 of 1.10.6 of Ant
Modified: dev/ant/README.html dev/ant/RELEASE-NOTES-1.10.6.html Modified: dev/ant/README.html ============================================================================== --- dev/ant/README.html (original) +++ dev/ant/README.html Thu May 2 13:53:36 2019 @@ -1,371 +1,120 @@ -Instructions for making a Release: - -Authors: Conor MacNeill - Stefan Bodewig - Magesh Umasankar - Antoine Levy-Lambert - -Note: This document was adapted from the one created in the context of - releasing Ant 1.9.7. It assumes the first release created from - master will be 1.10. - Please interpret the branch names, tags, etc. according to - your context. - - It reflects the way Stefan prefers to cut the release, parts of - this process haven't even been discussed on the dev list and may - change with later releases. - -1. Propose a release plan for vote. This should set out the timetable for - the release under ideal circumstances. - - In reality, you send a note to the list that you intend to cut the - release and wait for a few days whether anybody objects. - - We haven't created extra branches for releases in a long time and - with our new 1.9.x LTS policy there is a permanent branch for - Java5 compatible releases anyway. So no extra branch for the - releases is needed. - - This document assumes you are familiar with git - http://git-scm.com/book/en/v2/ - may be a good guide if you are not. - -2. Ensure you have all the external libraries that Ant uses in your - lib/optional directory. All dependencies are either provided by - JDK 1.8.0 or downloadable using - ant -f fetch.xml -Ddest=optional - To find out whether you have all the libraries you need, execute - the build with -verbose option and scan for lines beginning with - "Unable to load...". - - Also check the NOTICE file to make sure it has the correct - Copyright year. If the year isn't right, update that file to use - the right year and commit and push the change upstream, before - starting any release process. - - There are certain features that require JDK 9+ version to be used - while releasing Ant 1.10.x from master branch. Make sure JAVA_HOME - points to a JDK installation which is minimally Java 9. - -3. We don't want tags for failed votes to end up on our branches so - the release is first created from a detached head. - - Checkout the HEAD of the master branch as a detached head: - - $ git checkout master^0 - -4. Make sure that your directory tree is clean by running git status. - Some tests leave behind leftovers which end up in the source - distribution otherwise. - -5. Set the version number in several files to the required new - versions. These are: - - * manual/cover.html (version should already be correct here) - * manual/credits.html (version should already be correct here) - * build.xml properties : project.version,manifest-version,pom.version - * POM files under src/etc/poms and subdirectories - if you've got mvn installed - - $ mvn versions:set -DnewVersion=1.10.0 -DgenerateBackupPoms=false - - inside src/etc/poms should do the trick. - - * ivy.xml in release subdirectory (version should already be correct here) - * WHATSNEW (version should already be correct here) - * src/etc/testcases/taskdefs/conditions/antversion.xml (version should already be correct here) - -6. Next bootstrap, build and run the tests. - - $ ./bootstrap.sh - - Make sure the log messages doesn't contain the message: - - "Java 9+ features won't be available in the distribution" - - If it does, then it's a sign that JAVA_HOME isn't pointing to a JDK 9+ version. - Fix JAVA_HOME to point to a valid JDK 9+ version and redo the release steps. - - $ ./build.sh - $ ./build.sh test - # if you've got maven installed - $ mvn -f src/etc/poms/pom.xml -DskipTests package - -7. Then build the distribution. It is important that this be a clean - build. - - # clean - $ rm -rf bootstrap build dist distribution java-repository target - $ ./build.sh dist-lite - $ ./dist/bin/ant -nouserlib -lib lib/optional distribution - - build.xml specifies that the code should be compiled with - source=1.8 and target=1.8. - -8. Commit your changes, tag them, push them. - - $ git tag -s -m "Tagging RC1 for version 1.10.0 of Ant" ANT_1.10.0_RC1 - $ git push --tags - -9. Ensure that the GPG key you use is inside the KEYS file in Ant's - git repository - <https://gitbox.apache.org/repos/asf?p=ant-antlibs-common.git;a=blob;f=KEYS;h=dc62b011b1b429bd6de913f8f2bce79b715f96db;hb=HEAD> - - and that you copy the KEYS file to /www/www.apache.org/dist/ant - - Also make sure you have sent the key that you use to a public - keyserver. - -10. Sign the distribution files - - There are two aproaches, one uses Ant and a few libraries, the - other requires you to run gnupg manually. The first version didn't - work for Stefan when he built the first release candidate for - 1.9.7. - - a. Using the script release/signit.xml - - This script requires using commons-openpgp to sign the artefacts, - - This tool can be checked out from - http://svn.apache.org/repos/asf/commons/sandbox/openpgp/trunk - You have to build it using maven. - - $ mvn install - - The script assumes commons-openpgp (and bouncycastle) are in your - local maven repository. - - You can create a property file gnupg.properties in your home directory - with your key id - like - - keyid=5F6B8B72 - - or use -Dkeyid - - and pass your key passphrase on the command line with -Dpassword=**** - - $ ./build.sh -f release/signit.xml -Dpassword=**** - - b. Using gpg - - $ for i in distribution/*/*.zip distribution/*/*.gz distribution/*/*.bz2 distribution/*/*.xz; do gpg --use-agent --detach-sign --armor $i; done - $ for i in java-repository/org/apache/ant/ant*/*/*.jar java-repository/org/apache/ant/ant*/*/*.pom; do gpg --use-agent --detach-sign --armor $i; done - -11. Convert the part of the WHATSNEW file covering the changes - since the last release into HTML for the README file on the - website. See the previous release directories for examples of these files. - - Use the target txt2html of docs.xml - - $ ./build.sh -f docs.xml txt2html - - This target generates a file build/html/WHATSNEW.html - - Add an html head element with a title like "Release Notes of Apache Ant - 1.10.0" (from the default txt2html) - - Cut all sections about previous releases to keep only the current release, - and save as RELEASE-NOTES-1.10.0.html inside the distribution folder. - - Copy the contents of RELEASE-NOTES-1.10.0.html also into README.html - -12. The distribution is now ready to go. - Create a SVN sandbox on your computer with https://dist.apache.org/repos/dist/dev/ant in it - Copy the distribution folder to the location of the sandbox. - svn add the files and commit into https://dist.apache.org/repos/dist/dev/ant - -13. Upload the maven artifacts located under java-repository/org/apache/ant - these artifacts comprise currently for each ant jar of one POM - file, the corresponding jar file and the corresponding GPG - signatures (x.pom, x.jar, x.pom.asc, x.jar.asc) SHA1 are - generated by ivy during the upload - - to - - https://repository.apache.org (nexus repository) - - using the build file release/upload.xml - this requires Ivy - - $ ./build.sh -Dupload.user=foo -Dupload.password=secret -lib location_of_ivy_jar -f release/upload.xml - - After the upload, you need to access the web interface of nexus - under https://repository.apache.org login using your Apache - credentials in the left pane, below "build promotion", click on - the "Stagings Repositories" links expand org.apache.ant select the - checkbox next to the upload that you just did click the button - "Close" on the top of the table listing the uploads make a note of - the location of the staging repository for the vote email - -14. Once this is committed send a release vote email on dev@ant. - The email will typically mention : - - the git tag for the release including commit hash, - - the location of the tarballs, including revision number in - dist.apache.org repository - - the URL for the maven artifacts - - The vote will only pass if at least three PMC members have voted +1 - and more +1s than -1s have been cast. The vote will run for 3 days. - -15. If the vote fails, address the problems and recreate the next RC - build. - -16. Once the vote has passed, tag the last RC created with the final tag - - $ git tag -s -m "Tagging version 1.10.0 of Ant" rel/1.10.0 HASH_OF_LAST_RC - $ git push --tags - -17. The distrib artifacts should be published the apache dist. It is - managed via svnpubsub so the release should be committed to the - subversion repository - https://dist.apache.org/repos/dist/release/ant/. - - * commit the new release files to - - https://dist.apache.org/repos/dist/release/ant/[source|binaries|manual]. - - * Make https://dist.apache.org/repos/dist/release/ant/README.html - point to the new RELEASE-NOTES or a copy of it. - - * release the maven artifacts using the web interface of nexus under https://repository.apache.org - login using your Apache credentials - in the left pane, below "build promotion", click on the "Stagings Repositories" links - expand org.apache.ant - select the checkbox next to the upload that you just did - and click the button "Release". - 4 hours later, the artifacts will be in the maven central repository. - -18. Update the Apache Reporter System - - https://reporter.apache.org/addrelease.html?ant - -19. Address the available version tags in BugZilla. Create new - milestone 1.10.1 and version 1.10.0. - -20. Add a new release tag to doap_Ant.rdf in Ant's site. - -21. checkout the master branch, merge the tag but don't push the - commit - - [if a release of Ant 1.9.x happened at the same time, deal with - the 1.9.x tag on the 1.9.x branch first and merge the 1.9.x branch - to master before proceeding here] - - $ git checkout master - $ git merge rel/1.10.0 - - Set the version number in several files to the required version of - the next 1.10.x release. These are: - - * manual/cover.html - * manual/credits.html - * build.xml properties : project.version,manifest-version,pom.version - - project.version property in build.xml gets bumped to - [newversion]alpha, for example 1.10.1alpha - - manifest-version gets bumped to the exact next release number - for example 1.10.1. - - pom.version gets bumped to [newversion]-SNAPSHOT - for example 1.10.1-SNAPSHOT. - - * POM files under src/etc/poms and subdirectories - if you've got mvn installed - - $ mvn versions:set -DnewVersion=1.10.1-SNAPSHOT -DgenerateBackupPoms=false - - inside src/etc/poms should do the trick. - - * ivy.xml in release subdirectory - * WHATSNEW (add a new section) - * src/etc/testcases/taskdefs/conditions/antversion.xml - - Amend the merge commit - - $ git add -u - $ git commit -a --amend - $ git push - -22. wait a few hours for the mirrors to catch up - -23. Update the ant.apache.org site : - - The website is managed here: https://svn.apache.org/repos/asf/ant/site/ant/ - - Copy the manual of the release into the production folder - since - the site still uses svn and Ant proper uses git there currently is - no way to use the scm for this. - - [TODO once there is the first release of 1.10.0, we'll likely need - to restructure the site to allow two versions of the manual to - exist in parallel] - - Update the following files for version number: - - * source/antnews.xml (Announcement) - * source/faq.xml (Ant's history details - not for betas) - * source/index.xml (Announcement, latest release details, link to - manual under "Documentation") - * source/srcdownload.xml - * source/bindownload.xml - * source/manualdownload.xml - - Generate the html files by invoking 'ant' - Commit the modified/generated files in the 'production' folder, it will go - live on ant.apache.org in a matter on seconds. - -24. At this point in time, the release is done and announcements are made. - PGP-sign your announcement posts. - - Apache mailing lists that should get the announcements: - annou...@apache.org, dev@ant and user@ant. - -25. You can now reacquaint yourself with your family and friends. - -26. After a few days "svn rm" the older release artifacts and release - notes from https://dist.apache.org/repos/dist/release/ant/ - - "older" here means any older 1.10.x release but not the latest - 1.9.x release. - -Related Information - -http://www.apache.org/dev/#releases -http://commons.apache.org/releases/index.html -http://wiki.apache.org/commons/SigningReleases - -Files containing version information ------------------------------------- - - * manual/cover.html - * manual/credits.html - * build.xml properties : project.version,manifest-version,pom.version - * POM files under src/etc/poms and subdirectories - * ivy.xml in release subdirectory - * WHATSNEW - * src/etc/testcases/taskdefs/conditions/antversion.xml - -cover.html, credits.html, POM files, antversion.xml should be -adjusted for the [newversion] right after the build and tagging -of the release - -build.xml ---------- - - right before a release : - - the project.version gets bumped to the exact release - number, for instance 1.9.5 - - right after a release : - - project.version property in build.xml gets bumped to - [newversion]alpha, for example 1.9.6alpha - - manifest-version gets bumped to the exact next release number - for example 1.9.6 - - pom.version gets bumped to [newversion]-SNAPSHOT - - - +<html> +<head> + <title>Release Notes of Apache Ant 1.10.6</title> +</head> +<body><pre> +Changes from Ant 1.10.5 TO Ant 1.10.6 +===================================== + +Changes that could break older environments: +------------------------------------------- + + * image task no longer works on Java 9+ because internal classes + supporting Java Advanced Imaging are removed; imageio task (based on + ImageIO and AWT) is provided as a replacement. + + * junitlauncher task has changed the class names and package names of + the task as well as some of the supporting classes of that task. If + any code depended on these class or package names, they will have to + be updated to reference these newly named classes. This however, + doesn't impact build scripts if their reference to junitlauncher task + was merely through the use of the <junitlauncher> element. + + * ClearCase#runS has been augmented by a two arg-version and the + one-arg version will no longer be called. This may affect + subclasses that have overridden runS. + +Fixed bugs: +----------- + + * fetch.xml must retrieve runtime rather than compile dependencies for + mail task. + Bugzilla Report 62621 + + * Fixes an issue in junitreport task, which used to throw a + java.net.MalformedURLException when saxon was used on Windows OS. + Bugzilla Report 62594 + + * augment task now throws a BuildException (as noted in its manual) + instead of a IllegalStateException in the absence of the "id" attribute. + Bugzilla Report 62655 + + * org.apache.tools.zip.ZipOutputStream would sometimes potentially use + an incorrect compression level for a zip entry. This is now fixed. + Bugzilla Report 62686 + + * sync task, in some cases on case insensitive file systems, would consider + a file in a destination directory to be orphaned and would delete it. + This task has now been fixed to infer the case sensitivity of the filesystem + of the destination directory. + Bugzilla Report 62890 + + * Fixes a potential java.util.ConcurrentModificationException in + org.apache.tools.ant.Project#getCopyOfReferences. + Github Pull Request #81 + + * cccheckout would ignore an error of the "ls checkout" command even + if failOnError was set to false. + Bugzilla Report 63071 + + * The isreachable condition could in some cases return true even if the + actual address could potentially be unreachable. This is now fixed + and the resolved address is actually checked for reachability. + + * Fixes an issue where scp transfer completion tracking wasn't being + triggered for 100% completion. + Github Pull Request #91 + + +Other changes: +-------------- + * generatekey task now supports SubjectAlternativeName during key + generation. + + * the <modified> selector has a new built-in algorithm 'lastmodified' + which computes a value based upon the lastmodified time of the file. + + * junitlauncher task now supports running tests in a forked JVM. More + details available in the junitlauncher task manual. + + * signjar and verifyjar now support the -providerName, -providerClass + and -providerArg command line options of keytool via new attributes. + Bugzilla Report 65234 + + * signjar and verifyjar now supported nested <arg> elements for + command line arguments that are not supported explicitly by the + tasks via attributes. + + * added several attributes to <javadoc> that support modules. + Bugzilla Report 62424 + + * properties used or set by BuildFileTask/BuildFileRule are documented + in MagicTestNames. A new magic property, ant.test.basedir.ignore, is + introduced for cases where Ant projects set up for test purposes + must ignore basedir set externally by test harness. + + * a new CharSet type is provided for encoding or charset attributes in + tasks that must deal with different character encodings in files, + file names and other string resources. + + * org.apache.tools.ant.AntClassLoader is now multi-release jar aware. + Starting Java 9, jar files can be packaged as multi-release jars, + AntClassLoader now recognizes such multi-release jar files while + loading resources at runtime in Java 9+ runtime environments. + Bugzilla Report 62952 + + * Added jmod and link tasks, to support jmod and jlink tools of JDK 9+. + Github Pull Request #80 + + * Jsch library dependency has now been upgraded to 0.1.55. Jsch is + the library behind the sshexec and scp Ant tasks. + Github Pull Request #84 + + * The "http" condition, now has a "readTimeout" attribute which can be + used to control the amount of time to wait for the read to complete. + Bugzilla Report 63193 + + * ftp task manual has been updated to mention that the remote listing of + files honours the followsymlinks attribute. + Bugzilla Report 63226 +</pre></body></html> Modified: dev/ant/RELEASE-NOTES-1.10.6.html ============================================================================== --- dev/ant/RELEASE-NOTES-1.10.6.html (original) +++ dev/ant/RELEASE-NOTES-1.10.6.html Thu May 2 13:53:36 2019 @@ -1,371 +1,120 @@ -Instructions for making a Release: - -Authors: Conor MacNeill - Stefan Bodewig - Magesh Umasankar - Antoine Levy-Lambert - -Note: This document was adapted from the one created in the context of - releasing Ant 1.9.7. It assumes the first release created from - master will be 1.10. - Please interpret the branch names, tags, etc. according to - your context. - - It reflects the way Stefan prefers to cut the release, parts of - this process haven't even been discussed on the dev list and may - change with later releases. - -1. Propose a release plan for vote. This should set out the timetable for - the release under ideal circumstances. - - In reality, you send a note to the list that you intend to cut the - release and wait for a few days whether anybody objects. - - We haven't created extra branches for releases in a long time and - with our new 1.9.x LTS policy there is a permanent branch for - Java5 compatible releases anyway. So no extra branch for the - releases is needed. - - This document assumes you are familiar with git - http://git-scm.com/book/en/v2/ - may be a good guide if you are not. - -2. Ensure you have all the external libraries that Ant uses in your - lib/optional directory. All dependencies are either provided by - JDK 1.8.0 or downloadable using - ant -f fetch.xml -Ddest=optional - To find out whether you have all the libraries you need, execute - the build with -verbose option and scan for lines beginning with - "Unable to load...". - - Also check the NOTICE file to make sure it has the correct - Copyright year. If the year isn't right, update that file to use - the right year and commit and push the change upstream, before - starting any release process. - - There are certain features that require JDK 9+ version to be used - while releasing Ant 1.10.x from master branch. Make sure JAVA_HOME - points to a JDK installation which is minimally Java 9. - -3. We don't want tags for failed votes to end up on our branches so - the release is first created from a detached head. - - Checkout the HEAD of the master branch as a detached head: - - $ git checkout master^0 - -4. Make sure that your directory tree is clean by running git status. - Some tests leave behind leftovers which end up in the source - distribution otherwise. - -5. Set the version number in several files to the required new - versions. These are: - - * manual/cover.html (version should already be correct here) - * manual/credits.html (version should already be correct here) - * build.xml properties : project.version,manifest-version,pom.version - * POM files under src/etc/poms and subdirectories - if you've got mvn installed - - $ mvn versions:set -DnewVersion=1.10.0 -DgenerateBackupPoms=false - - inside src/etc/poms should do the trick. - - * ivy.xml in release subdirectory (version should already be correct here) - * WHATSNEW (version should already be correct here) - * src/etc/testcases/taskdefs/conditions/antversion.xml (version should already be correct here) - -6. Next bootstrap, build and run the tests. - - $ ./bootstrap.sh - - Make sure the log messages doesn't contain the message: - - "Java 9+ features won't be available in the distribution" - - If it does, then it's a sign that JAVA_HOME isn't pointing to a JDK 9+ version. - Fix JAVA_HOME to point to a valid JDK 9+ version and redo the release steps. - - $ ./build.sh - $ ./build.sh test - # if you've got maven installed - $ mvn -f src/etc/poms/pom.xml -DskipTests package - -7. Then build the distribution. It is important that this be a clean - build. - - # clean - $ rm -rf bootstrap build dist distribution java-repository target - $ ./build.sh dist-lite - $ ./dist/bin/ant -nouserlib -lib lib/optional distribution - - build.xml specifies that the code should be compiled with - source=1.8 and target=1.8. - -8. Commit your changes, tag them, push them. - - $ git tag -s -m "Tagging RC1 for version 1.10.0 of Ant" ANT_1.10.0_RC1 - $ git push --tags - -9. Ensure that the GPG key you use is inside the KEYS file in Ant's - git repository - <https://gitbox.apache.org/repos/asf?p=ant-antlibs-common.git;a=blob;f=KEYS;h=dc62b011b1b429bd6de913f8f2bce79b715f96db;hb=HEAD> - - and that you copy the KEYS file to /www/www.apache.org/dist/ant - - Also make sure you have sent the key that you use to a public - keyserver. - -10. Sign the distribution files - - There are two aproaches, one uses Ant and a few libraries, the - other requires you to run gnupg manually. The first version didn't - work for Stefan when he built the first release candidate for - 1.9.7. - - a. Using the script release/signit.xml - - This script requires using commons-openpgp to sign the artefacts, - - This tool can be checked out from - http://svn.apache.org/repos/asf/commons/sandbox/openpgp/trunk - You have to build it using maven. - - $ mvn install - - The script assumes commons-openpgp (and bouncycastle) are in your - local maven repository. - - You can create a property file gnupg.properties in your home directory - with your key id - like - - keyid=5F6B8B72 - - or use -Dkeyid - - and pass your key passphrase on the command line with -Dpassword=**** - - $ ./build.sh -f release/signit.xml -Dpassword=**** - - b. Using gpg - - $ for i in distribution/*/*.zip distribution/*/*.gz distribution/*/*.bz2 distribution/*/*.xz; do gpg --use-agent --detach-sign --armor $i; done - $ for i in java-repository/org/apache/ant/ant*/*/*.jar java-repository/org/apache/ant/ant*/*/*.pom; do gpg --use-agent --detach-sign --armor $i; done - -11. Convert the part of the WHATSNEW file covering the changes - since the last release into HTML for the README file on the - website. See the previous release directories for examples of these files. - - Use the target txt2html of docs.xml - - $ ./build.sh -f docs.xml txt2html - - This target generates a file build/html/WHATSNEW.html - - Add an html head element with a title like "Release Notes of Apache Ant - 1.10.0" (from the default txt2html) - - Cut all sections about previous releases to keep only the current release, - and save as RELEASE-NOTES-1.10.0.html inside the distribution folder. - - Copy the contents of RELEASE-NOTES-1.10.0.html also into README.html - -12. The distribution is now ready to go. - Create a SVN sandbox on your computer with https://dist.apache.org/repos/dist/dev/ant in it - Copy the distribution folder to the location of the sandbox. - svn add the files and commit into https://dist.apache.org/repos/dist/dev/ant - -13. Upload the maven artifacts located under java-repository/org/apache/ant - these artifacts comprise currently for each ant jar of one POM - file, the corresponding jar file and the corresponding GPG - signatures (x.pom, x.jar, x.pom.asc, x.jar.asc) SHA1 are - generated by ivy during the upload - - to - - https://repository.apache.org (nexus repository) - - using the build file release/upload.xml - this requires Ivy - - $ ./build.sh -Dupload.user=foo -Dupload.password=secret -lib location_of_ivy_jar -f release/upload.xml - - After the upload, you need to access the web interface of nexus - under https://repository.apache.org login using your Apache - credentials in the left pane, below "build promotion", click on - the "Stagings Repositories" links expand org.apache.ant select the - checkbox next to the upload that you just did click the button - "Close" on the top of the table listing the uploads make a note of - the location of the staging repository for the vote email - -14. Once this is committed send a release vote email on dev@ant. - The email will typically mention : - - the git tag for the release including commit hash, - - the location of the tarballs, including revision number in - dist.apache.org repository - - the URL for the maven artifacts - - The vote will only pass if at least three PMC members have voted +1 - and more +1s than -1s have been cast. The vote will run for 3 days. - -15. If the vote fails, address the problems and recreate the next RC - build. - -16. Once the vote has passed, tag the last RC created with the final tag - - $ git tag -s -m "Tagging version 1.10.0 of Ant" rel/1.10.0 HASH_OF_LAST_RC - $ git push --tags - -17. The distrib artifacts should be published the apache dist. It is - managed via svnpubsub so the release should be committed to the - subversion repository - https://dist.apache.org/repos/dist/release/ant/. - - * commit the new release files to - - https://dist.apache.org/repos/dist/release/ant/[source|binaries|manual]. - - * Make https://dist.apache.org/repos/dist/release/ant/README.html - point to the new RELEASE-NOTES or a copy of it. - - * release the maven artifacts using the web interface of nexus under https://repository.apache.org - login using your Apache credentials - in the left pane, below "build promotion", click on the "Stagings Repositories" links - expand org.apache.ant - select the checkbox next to the upload that you just did - and click the button "Release". - 4 hours later, the artifacts will be in the maven central repository. - -18. Update the Apache Reporter System - - https://reporter.apache.org/addrelease.html?ant - -19. Address the available version tags in BugZilla. Create new - milestone 1.10.1 and version 1.10.0. - -20. Add a new release tag to doap_Ant.rdf in Ant's site. - -21. checkout the master branch, merge the tag but don't push the - commit - - [if a release of Ant 1.9.x happened at the same time, deal with - the 1.9.x tag on the 1.9.x branch first and merge the 1.9.x branch - to master before proceeding here] - - $ git checkout master - $ git merge rel/1.10.0 - - Set the version number in several files to the required version of - the next 1.10.x release. These are: - - * manual/cover.html - * manual/credits.html - * build.xml properties : project.version,manifest-version,pom.version - - project.version property in build.xml gets bumped to - [newversion]alpha, for example 1.10.1alpha - - manifest-version gets bumped to the exact next release number - for example 1.10.1. - - pom.version gets bumped to [newversion]-SNAPSHOT - for example 1.10.1-SNAPSHOT. - - * POM files under src/etc/poms and subdirectories - if you've got mvn installed - - $ mvn versions:set -DnewVersion=1.10.1-SNAPSHOT -DgenerateBackupPoms=false - - inside src/etc/poms should do the trick. - - * ivy.xml in release subdirectory - * WHATSNEW (add a new section) - * src/etc/testcases/taskdefs/conditions/antversion.xml - - Amend the merge commit - - $ git add -u - $ git commit -a --amend - $ git push - -22. wait a few hours for the mirrors to catch up - -23. Update the ant.apache.org site : - - The website is managed here: https://svn.apache.org/repos/asf/ant/site/ant/ - - Copy the manual of the release into the production folder - since - the site still uses svn and Ant proper uses git there currently is - no way to use the scm for this. - - [TODO once there is the first release of 1.10.0, we'll likely need - to restructure the site to allow two versions of the manual to - exist in parallel] - - Update the following files for version number: - - * source/antnews.xml (Announcement) - * source/faq.xml (Ant's history details - not for betas) - * source/index.xml (Announcement, latest release details, link to - manual under "Documentation") - * source/srcdownload.xml - * source/bindownload.xml - * source/manualdownload.xml - - Generate the html files by invoking 'ant' - Commit the modified/generated files in the 'production' folder, it will go - live on ant.apache.org in a matter on seconds. - -24. At this point in time, the release is done and announcements are made. - PGP-sign your announcement posts. - - Apache mailing lists that should get the announcements: - annou...@apache.org, dev@ant and user@ant. - -25. You can now reacquaint yourself with your family and friends. - -26. After a few days "svn rm" the older release artifacts and release - notes from https://dist.apache.org/repos/dist/release/ant/ - - "older" here means any older 1.10.x release but not the latest - 1.9.x release. - -Related Information - -http://www.apache.org/dev/#releases -http://commons.apache.org/releases/index.html -http://wiki.apache.org/commons/SigningReleases - -Files containing version information ------------------------------------- - - * manual/cover.html - * manual/credits.html - * build.xml properties : project.version,manifest-version,pom.version - * POM files under src/etc/poms and subdirectories - * ivy.xml in release subdirectory - * WHATSNEW - * src/etc/testcases/taskdefs/conditions/antversion.xml - -cover.html, credits.html, POM files, antversion.xml should be -adjusted for the [newversion] right after the build and tagging -of the release - -build.xml ---------- - - right before a release : - - the project.version gets bumped to the exact release - number, for instance 1.9.5 - - right after a release : - - project.version property in build.xml gets bumped to - [newversion]alpha, for example 1.9.6alpha - - manifest-version gets bumped to the exact next release number - for example 1.9.6 - - pom.version gets bumped to [newversion]-SNAPSHOT - - - +<html> +<head> + <title>Release Notes of Apache Ant 1.10.6</title> +</head> +<body><pre> +Changes from Ant 1.10.5 TO Ant 1.10.6 +===================================== + +Changes that could break older environments: +------------------------------------------- + + * image task no longer works on Java 9+ because internal classes + supporting Java Advanced Imaging are removed; imageio task (based on + ImageIO and AWT) is provided as a replacement. + + * junitlauncher task has changed the class names and package names of + the task as well as some of the supporting classes of that task. If + any code depended on these class or package names, they will have to + be updated to reference these newly named classes. This however, + doesn't impact build scripts if their reference to junitlauncher task + was merely through the use of the <junitlauncher> element. + + * ClearCase#runS has been augmented by a two arg-version and the + one-arg version will no longer be called. This may affect + subclasses that have overridden runS. + +Fixed bugs: +----------- + + * fetch.xml must retrieve runtime rather than compile dependencies for + mail task. + Bugzilla Report 62621 + + * Fixes an issue in junitreport task, which used to throw a + java.net.MalformedURLException when saxon was used on Windows OS. + Bugzilla Report 62594 + + * augment task now throws a BuildException (as noted in its manual) + instead of a IllegalStateException in the absence of the "id" attribute. + Bugzilla Report 62655 + + * org.apache.tools.zip.ZipOutputStream would sometimes potentially use + an incorrect compression level for a zip entry. This is now fixed. + Bugzilla Report 62686 + + * sync task, in some cases on case insensitive file systems, would consider + a file in a destination directory to be orphaned and would delete it. + This task has now been fixed to infer the case sensitivity of the filesystem + of the destination directory. + Bugzilla Report 62890 + + * Fixes a potential java.util.ConcurrentModificationException in + org.apache.tools.ant.Project#getCopyOfReferences. + Github Pull Request #81 + + * cccheckout would ignore an error of the "ls checkout" command even + if failOnError was set to false. + Bugzilla Report 63071 + + * The isreachable condition could in some cases return true even if the + actual address could potentially be unreachable. This is now fixed + and the resolved address is actually checked for reachability. + + * Fixes an issue where scp transfer completion tracking wasn't being + triggered for 100% completion. + Github Pull Request #91 + + +Other changes: +-------------- + * generatekey task now supports SubjectAlternativeName during key + generation. + + * the <modified> selector has a new built-in algorithm 'lastmodified' + which computes a value based upon the lastmodified time of the file. + + * junitlauncher task now supports running tests in a forked JVM. More + details available in the junitlauncher task manual. + + * signjar and verifyjar now support the -providerName, -providerClass + and -providerArg command line options of keytool via new attributes. + Bugzilla Report 65234 + + * signjar and verifyjar now supported nested <arg> elements for + command line arguments that are not supported explicitly by the + tasks via attributes. + + * added several attributes to <javadoc> that support modules. + Bugzilla Report 62424 + + * properties used or set by BuildFileTask/BuildFileRule are documented + in MagicTestNames. A new magic property, ant.test.basedir.ignore, is + introduced for cases where Ant projects set up for test purposes + must ignore basedir set externally by test harness. + + * a new CharSet type is provided for encoding or charset attributes in + tasks that must deal with different character encodings in files, + file names and other string resources. + + * org.apache.tools.ant.AntClassLoader is now multi-release jar aware. + Starting Java 9, jar files can be packaged as multi-release jars, + AntClassLoader now recognizes such multi-release jar files while + loading resources at runtime in Java 9+ runtime environments. + Bugzilla Report 62952 + + * Added jmod and link tasks, to support jmod and jlink tools of JDK 9+. + Github Pull Request #80 + + * Jsch library dependency has now been upgraded to 0.1.55. Jsch is + the library behind the sshexec and scp Ant tasks. + Github Pull Request #84 + + * The "http" condition, now has a "readTimeout" attribute which can be + used to control the amount of time to wait for the read to complete. + Bugzilla Report 63193 + + * ftp task manual has been updated to mention that the remote listing of + files honours the followsymlinks attribute. + Bugzilla Report 63226 +</pre></body></html>