commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject [VOTE] Release Apache Commons VFS Project 2.4.1 based on RC1
Date Sun, 11 Aug 2019 12:50:27 GMT
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: (svn
revision 35198)

The Git tag commons-vfs-2.4.1-RC1 commit for this RC is
eabdee306d5b0a73859a0aa841a5c0ccfe8b337a which you can browse here:;a=commit;h=eabdee306d5b0a73859a0aa841a5c0ccfe8b337a
You may checkout this tag using:
    git clone --branch
commons-vfs-2.4.1-RC1 commons-vfs-2.4.1-RC1

Maven artifacts are here:

These are the artifacts and their hashes:

(SHA1: d334baee497ee14d78581a1f4dc2ef203744ba34)
(SHA1: 0daef39eeb8130c35d5341f9cb863b31496b245b)
(SHA1: f9abe836aedb9e78c784bec4a98d72af95d664ef)
(SHA1: 7e065d5b0d06f5bc809d867f4ee212fd12e301d5)
(SHA1: 80b0fec7213ddeb627193fcf570e7d961aa88048)
(SHA1: 2b041628c3cb436d8eee25f78603f04eb5e817a5)
(SHA1: 9239c38d59560a76eea5108bb92622cf9e0d2f2d)
(SHA1: 7a8f46ba636106c51512cb319c782fcdf242c009)
(SHA1: baca67a9f6be69b52869c2ec49b7487bdbd6bc9f)
(SHA1: dcbb400154bb7ee1868fa0f2e800b7fd910be68f)
(SHA1: 0d75228dbd15638c135c4afa914b46a520425b83)
(SHA1: ef6cf5ae11caacfff78cf9d25387dd847593d61a)
(SHA1: 1eafbd241b3be42f3ac012f82b156de8319953a0)
(SHA1: 79df4540ba2fb5a33cdccfa4228a16215d290763)
(SHA1: a7c5c5dc0f5dd83f8bc58ef0c50f3c1d336fd86e)

I have tested this with 'mvn -V clean install site -P japicmp' using:

Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
Maven home: C:\Java\apache-maven-3.6.1\bin\..
Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program
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:

    (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):

RAT Report:


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 --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

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-

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message