Am 22.10.2013 18:48, schrieb Gary Gregory: > Hen: Welcome back to the release mud pit! ;) > > I am looking at your site and I also checked out the tag and built it. > > -1 > > The site, at the top says "Version 1.10-RC1", it should say "Version: 1.10". > > This is because the POM still says 1.10-RC1 instead of 1.10. > > This would also explain this: > > [WARNING] Downloading from JIRA failed. Received: [400] > [WARNING] JIRA file > C:\temp\rc\CONFIGURATION_1_10RC1\target\jira-results.xml doesn't exist. > [WARNING] > org.apache.maven.plugin.MojoExecutionException: Couldn't find any issues > for the version '1.10-RC1' among the supplied issues: [] > > The logo is missing its "TM" per Apache branding. > > When I run "mvn site" I get a unit test error but the build does not fail, > which I do not understand: > > Running org.apache.commons.configuration.TestDataConfiguration > Tests run: 50, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec > <<< FAILURE! - in org.apache.commons.configuration.TestDataConfiguration > testGetInetAddressInvalidType(org.apache.commons.configuration.TestDataConfiguration) > Time elapsed: 0 sec <<< FAILURE! > java.lang.AssertionError: Expected exception: > org.apache.commons.configuration.ConversionException > at > org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > RAT and Clirr reports are clean. > > Cobertura reports the following have 0% test code coverage: > > - AppletConfiguration > - HierarchicalXMLConfiguration > - TokenMgrError
HierarchicalXMLConfiguration is an empty deprecated class (it was renamed long ago to XMLConfiguration and exists only for backwards compatibility). TokenMgrError is generated using JavaCC. For AppletConfiguration a test class exists. However, the test checks whether an applet can be created. If not, no tests are executed. So maybe the test was run in an environment which does not support applets? Oliver > > This might not be a blocker but it does not inspire confidence. > > Other reports look good. > > My setup: > > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 > 11:22:22-0400) > Maven home: C:\Java\apache-maven-3.1.1\bin\.. > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_45\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > > Gary > > > On Tue, Oct 22, 2013 at 6:10 AM, Henning Schmiedehausen < > henn...@schmiedehausen.org> wrote: > >> [haven't done that in a long time. Please bear with me...] >> >> Bug fixes and minor enhancements from configuration 1.9. >> >> So I would like to release configuration 1.10. >> >> Configuration 1.10 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/configuration/ (svn >> revision >> 3321) >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-019/commons-configuration/commons-configuration/1.10-RC1/ >> >> Details of changes since 1.9 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES-1.10-RC1.txt >> Changes file: >> >> http://people.apache.org/~henning/configuration-1.10-RC1/changes-report.html >> >> Site: http://people.apache.org/~henning/configuration-1.10-RC1/ (The JIRA >> report will be fixed for the release) >> >> The tag is here: >> >> http://svn.apache.org/viewvc/commons/proper/configuration/tags/CONFIGURATION_1_10RC1/(svn >> revision 1534569) >> >> Clirr Report (compared to 1.9): >> http://people.apache.org/~henning/configuration-1.10-RC1/clirr-report.html >> RAT Report: >> http://people.apache.org/~henning/configuration-1.10-RC1/rat-report.html >> >> KEYS: http://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. after 1100 GMT >> 25-Oct 2013 >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but really should fix... >> [ ] -1 I oppose this release because... >> >> >> Thanks! >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
