Hi Oliver,

> Am 14.10.2017 um 21:28 schrieb Oliver Heger <oliver.he...@oliver-heger.de>:
> 
> Hi Benedikt,
> 
> it seems that the binary artifact does not contain the real classes, but
> classes manipulated by Cobertura. commons-io-2.6.jar contains a
> cobertura.properties file, and opening a class in a decompiler shows
> some Cobertura-specific initialization code.
> 
> Can you please double-check?

Wow, good catch! I think this is the second time something like that happens to 
me. I assume it happened because I built the site from the tag and then 
directly called mvn deploy without running clean. I will update the release 
documentation and push out a new RC.

Thank you!
Benedikt

> 
> Oliver
> 
> Am 14.10.2017 um 14:35 schrieb Benedikt Ritter:
>> Hello,
>> 
>> we have fixed quite a few bugs and added some nice new features since Apache 
>> Commons IO 2.5 was released, so I would like to release Apache Commons IO 
>> 2.6 based on RC2.
>> 
>> The changes since RC1 are:
>> - Worked on the design of the ByteOrderParser class
>> - Fixed IO-546
>> - Fixed IO-553
>> 
>> Commons IO 2.6 RC1 is available for review here: 
>> https://dist.apache.org/repos/dist/dev/commons/io/commons-io-2.6-RC2 (svn 
>> revision 22474)
>> 
>> The tag is here: 
>> https://git-wip-us.apache.org/repos/asf?p=commons-io.git;a=tag;h=dbd097debffe1b8c91d232a2311c08ff3e70e7a1
>> 
>> Commit ID the tag points at: a219081780bb1714876ef3e1109283b96f3b007b
>> 
>> Maven Artifacts: 
>> https://repository.apache.org/content/repositories/orgapachecommons-1276
>> 
>> These are the Maven artifacts and their hashes:
>> 
>> /commons-io/commons-io/2.6/commons-io-2.6-test-sources.jar.asc
>> (SHA1: 2a6e16c3f135851b5a907bd50655db9f9bff73a2)
>> /commons-io/commons-io/2.6/commons-io-2.6.pom.asc
>> (SHA1: 177e5b7e423cb9747f5b3cb982af326d24698c64)
>> /commons-io/commons-io/2.6/commons-io-2.6-tests.jar.asc
>> (SHA1: 38ccc2062ed998df95910eda9982e5c9623eb8cc)
>> /commons-io/commons-io/2.6/commons-io-2.6.pom
>> (SHA1: 5060835593e5b6ed18c82fc2e782f0a3c30a00b1)
>> /commons-io/commons-io/2.6/commons-io-2.6.jar.asc
>> (SHA1: 7a389502e94871e30f3330634925dff61e4e098a)
>> /commons-io/commons-io/2.6/commons-io-2.6-test-sources.jar
>> (SHA1: 75c8aa60dc4623dca0311b38f317ba56596a70ec)
>> /commons-io/commons-io/2.6/commons-io-2.6-javadoc.jar
>> (SHA1: 2d1132e48d5d2b698cc27290758dca7905031cfa)
>> /commons-io/commons-io/2.6/commons-io-2.6-sources.jar
>> (SHA1: db473f690e219b0566e7f1a8a991bf0e6f08a3c6)
>> /commons-io/commons-io/2.6/commons-io-2.6-tests.jar
>> (SHA1: 02a08a358025f15d44b5f0aaaa4410d89b413b97)
>> /commons-io/commons-io/2.6/commons-io-2.6.jar
>> (SHA1: adac173d974250643940c7836caf2726f11a0dc0)
>> /commons-io/commons-io/2.6/commons-io-2.6-javadoc.jar.asc
>> (SHA1: 7d78d02ce0d96c511de696b518f1c12133662417)
>> /commons-io/commons-io/2.6/commons-io-2.6-sources.jar.asc
>> (SHA1: 8debf732bc0e5187432f723c01503d75145dbd19)
>> 
>> I have tested this with JDK 8 using Maven 3.5.0.
>> 
>> Details of changes since 2.5 are in the release notes:
>> https://dist.apache.org/repos/dist/dev/commons/io/commons-io-2.6-RC2/RELEASE-NOTES.txt
>> http://home.apache.org/~britter/commons/commons-io-2.6-RC2/changes-report.html
>> 
>> I’ve already realized that I messed up the changes.xml: It has the wrong 
>> release date. I think we can fix this after the release since it is used to 
>> generate the website.
>> 
>> Site:
>> http://home.apache.org/~britter/commons/commons-io-2.6-RC2/ 
>> (note some *relative* links are broken and the 2.6 directories are not yet 
>> created - these will be OK once the site is deployed)
>> 
>> Clirr Report (compared to 2.5):
>> http://home.apache.org/~britter/commons/commons-io-2.6-RC2//clirr-report.html
>> 
>> RAT Report:
>> http://home.apache.org/~britter/commons/commons-io-2.6-RC2/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, i.e. sometime after 15:00 CEST (UTC+2) 17-October 
>> 2017
>> 
>> [ ] +1 Release these artifacts
>> [ ] +0 OK, but…
>> [ ] -0 OK, but really should fix…
>> [ ] -1 I oppose this release because...
>> 
>> Thanks!
>> 
>> Benedikt  
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to