I have had this build pass twice, running mvn -V clean install site -P japicmp
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: /usr/local/Cellar/maven/3.6.1/libexec Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac" I do however see a bunch of errors and warnings in the build, that while they do not fail the build, may or may not be known, as well as things like: There are 526 errors reported by Checkstyle 8.23 with /Users/ottofowler/tmp/commons-vfs–2.4.1-RC1/commons-vfs–2.4.1-RC1/checkstyle.xml ruleset.` And errors building models for http-client–3 etc. Here is the gist of my build log: commons-vfs–2.4.1-RC1-build.log <https://gist.github.com/ottobackwards/47c2413414cd1584b6f9aa7c9f166bfa> On August 11, 2019 at 08:50:42, Gary Gregory (ggreg...@apache.org) wrote: We have fixed 2 bugs and enhanced Javadocs since Apache Commons VFS 2.4 was released, so I would like to release Apache Commons VFS 2.4.1. Apache Commons VFS 2.4.1 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1 (svn revision 35198) The Git tag commons-vfs-2.4.1-RC1 commit for this RC is eabdee306d5b0a73859a0aa841a5c0ccfe8b337a which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-vfs.git;a=commit;h=eabdee306d5b0a73859a0aa841a5c0ccfe8b337a You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-vfs.git --branch commons-vfs-2.4.1-RC1 commons-vfs-2.4.1-RC1 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1458/org/apache/commons/commons-vfs2/2.4.1/ These are the artifacts and their hashes: /org/apache/commons/commons-vfs2-distribution/2.4.1/commons-vfs2-distribution-2.4.1.pom (SHA1: d334baee497ee14d78581a1f4dc2ef203744ba34) /org/apache/commons/commons-vfs2-distribution/2.4.1/commons-vfs2-distribution-2.4.1-javadoc.jar (SHA1: 0daef39eeb8130c35d5341f9cb863b31496b245b) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1-test-sources.jar (SHA1: f9abe836aedb9e78c784bec4a98d72af95d664ef) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1-javadoc.jar (SHA1: 7e065d5b0d06f5bc809d867f4ee212fd12e301d5) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1.pom (SHA1: 80b0fec7213ddeb627193fcf570e7d961aa88048) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1.jar (SHA1: 2b041628c3cb436d8eee25f78603f04eb5e817a5) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1-tests.jar (SHA1: 9239c38d59560a76eea5108bb92622cf9e0d2f2d) /org/apache/commons/commons-vfs2/2.4.1/commons-vfs2-2.4.1-sources.jar (SHA1: 7a8f46ba636106c51512cb319c782fcdf242c009) /org/apache/commons/commons-vfs2-project/2.4.1/commons-vfs2-project-2.4.1-site.xml (SHA1: baca67a9f6be69b52869c2ec49b7487bdbd6bc9f) /org/apache/commons/commons-vfs2-project/2.4.1/commons-vfs2-project-2.4.1-javadoc.jar (SHA1: dcbb400154bb7ee1868fa0f2e800b7fd910be68f) /org/apache/commons/commons-vfs2-project/2.4.1/commons-vfs2-project-2.4.1.pom (SHA1: 0d75228dbd15638c135c4afa914b46a520425b83) /org/apache/commons/commons-vfs2-examples/2.4.1/commons-vfs2-examples-2.4.1-javadoc.jar (SHA1: ef6cf5ae11caacfff78cf9d25387dd847593d61a) /org/apache/commons/commons-vfs2-examples/2.4.1/commons-vfs2-examples-2.4.1-sources.jar (SHA1: 1eafbd241b3be42f3ac012f82b156de8319953a0) /org/apache/commons/commons-vfs2-examples/2.4.1/commons-vfs2-examples-2.4.1.pom (SHA1: 79df4540ba2fb5a33cdccfa4228a16215d290763) /org/apache/commons/commons-vfs2-examples/2.4.1/commons-vfs2-examples-2.4.1.jar (SHA1: a7c5c5dc0f5dd83f8bc58ef0c50f3c1d336fd86e) I have tested this with 'mvn -V clean install site -P japicmp' using: Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: C:\Java\apache-maven-3.6.1\bin\.. Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_221\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Details of changes since 2.4 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1/site/index.html (note some *relative* links are broken and the 2.4.1 directories are not yet created - these will be OK once the site is deployed.) JApiCmp Report (compared to 2.4): https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1/site/commons-vfs2/japicmp.html RAT Report: https://dist.apache.org/repos/dist/dev/commons/vfs/2.4.1-RC1/site/rat-report.html KEYS: https://www.apache.org/dist/commons/KEYS Please review the release candidate and vote. This vote will close no sooner that 72 hours from now. [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release because... Thank you, Gary Gregory, Release Manager (using key 86fdc7e2a11262cb) For following is intended as a helper and refresher for reviewers. Validating a release candidate ============================== These guidelines are NOT complete. Requirements: Git, Java, Maven. You can validate a release from a release candidate (RC) tag as follows. 1) Clone and checkout the RC tag git clone https://gitbox.apache.org/repos/asf/commons-vfs.git --branch commons-vfs-2.4.1-RC1 commons-vfs-2.4.1-RC1 cd commons-vfs-2.4.1-RC1 2) Check Apache licenses This step is not required if the site includes a RAT report page which you then must check. mvn apache-rat:check 3) Check binary compatibility Newer components use JApiCmp with the japicmp Maven Profile: This step is not required if the site includes a JApiCmp report page which you then must check. mvn install -DskipTests -P japicmp japicmp:cmp 4) Build the package mvn -V clean package You can record the Maven and Java version produced by -V in your VOTE reply. To gather OS information from a command line: Windows: ver Linux: uname -a 5) Build the site for a single module project Note: Some plugins require the components to be installed instead of packaged. mvn site Check the site reports in: - Windows: target\site\index.html - Linux: target/site/index.html 6) Build the site for a multi-module project mvn site mvn site:stage Check the site reports in: - Windows: target\site\index.html - Linux: target/site/index.html -the end-
