summaryrefslogtreecommitdiff
path: root/ReleaseInstructions
diff options
context:
space:
mode:
authorJaikiran Pai <jaikiran@apache.org>2019-03-19 11:00:22 +0530
committerJaikiran Pai <jaikiran@apache.org>2019-03-19 11:00:22 +0530
commit508e0f3facef2552d06b56d39d7208fcd62d49ba (patch)
tree00b01aa639f41145c3b02483cffe9f178bc6f9b3 /ReleaseInstructions
parentaf8ddc9a3daf2960b8eac08d56e412c23a5b7591 (diff)
downloadant-508e0f3facef2552d06b56d39d7208fcd62d49ba.tar.gz
Make it easier, during release, to verify that JDK9+ is being used
Diffstat (limited to 'ReleaseInstructions')
-rw-r--r--ReleaseInstructions12
1 files changed, 12 insertions, 0 deletions
diff --git a/ReleaseInstructions b/ReleaseInstructions
index 9d25fb455..3c5f1e5c1 100644
--- a/ReleaseInstructions
+++ b/ReleaseInstructions
@@ -43,6 +43,10 @@ Note: This document was adapted from the one created in the context of
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.
@@ -74,6 +78,14 @@ Note: This document was adapted from the one created in the context of
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