Le 26/12/2014 16:00, Benedikt Ritter a écrit : > Hello, > > We have received some requests to release the fixes we habe implemented in > Commons Validator since 1.4 was released, so I would like to release > Validator 1.4.1. Validator 1.4.1 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/validator/ (svn revision > 7587) Maven artifacts are here: > https://repository.apache.org/content/repositories/orgapachecommons-1071/commons-validator/commons-validator/1.4.1/ > Details of changes since 1.4 are in the release notes: > https://dist.apache.org/repos/dist/dev/commons/validator/RELEASE-NOTES.txt > I have tested this with JDK 1.6, 1.7, 1.8 and 1.9 EA using maven 3.2.5. > Note that the build doesn't work with JDK 1.9 EA, since source and target > option 1.4 have been removed in JDK 1.9. The tag is here: > http://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_4_1_RC1/ > (svn revision 1647978) Site: no site - I'm currently having trouble to > login to people.apache.org, so I was unable to upload the site. Please > build the site yourself using mvn clean site. Clirr Report (compared to > 1.1): see above RAT Report: see above 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. after 2014/12/29 16:00 CET [ ] +1 Release these artifacts [ ] +0 OK, > but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release > because... Thanks! Benedikt
+1. I found lots of differences between the source artifacts and the tag, but all were false positive due to date formatting in subversion (and even RCS!) keywords. This is not a problem, just an annoyance while checking the release. There was an encoding problem when creating RELEASE-NOTES.txt from changes.xml as some contributor names got mangled. The names appear to have proper UTF-8 encoding in the xml file but were replaced by an ASCII question mark (0x3F) in the text file (not even the unicode replacement character 0xFFFD). This can be fixed by adding the following property in pom.xml: <commons.encoding>UTF-8</commons.encoding> and generating the announcement again. You should consider it if you roll another RC. best regards, Luc > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
