Luc Maisonobe schrieb:
Oliver Heger a écrit :
This is a vote for releasing Commons Configuration 1.6.
A first release candidate was created, the artifacts (including release
notes and a clirr report) can be found here:
http://people.apache.org/~oheger/configuration-1.6rc1/
When building from source with maven 2, compilation, tests and site
generation completed successfully. The problems I see are:
- 1 checkstyle error (minor)
- 17 bugs and 115 errors found by findbugs
(it is not enabled in the pom file, I added it when compiling
locally) at first glance, most of them seem easy to fix
- lots of complaints from RAT report due to missing licence headers,
this may be due to generated files that do not require licence but
are not listed in the RAT plugin configuration (there is no specific
configuration in the pom)
Would it be possible to fix some of the errors reported by findbugs and
RAT before release ?
Thanks for your feedback, Luc.
I will have a look at the RAT and findbugs issues. Strange enough the
findbugs report generated by the Maven 1 build is clean, but maybe it
uses an old version of findbugs.
Oliver
The site for 1.6 is also available at
http://people.apache.org/~oheger/configuration-1.6rc1/site/
The corresponding tag in svn is
http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_1_6RC1/
Note: The distributions are still created using Maven 1 (mainly because
I know how to do it and have a working setup from the last releases).
The main jar however was built with Maven 2 to get all the manifest
entries provided by the commons parent pom.
Please cast your votes.
TIA
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
