I think that’s it….I can re-tag if need be. I don’t think the git hash will change.
-Rob > On Mar 11, 2019, at 12:37 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > The tag looks wrong here: > > https://gitbox.apache.org/repos/asf?p=commons-build-plugin.git;a=commit;h=5f477eeb76bfc16dd2d31f9b75bb9d6ebd7a1b52 > > it is called commons-release-plugin-1.10-RC2 instead > of commons-build-plugin-1.10-RC2. > > Is anything else off in git land? > > Gary > > > On Sat, Mar 9, 2019 at 8:33 PM Rob Tompkins <chtom...@gmail.com> wrote: > >> We have fixed quite a few bugs and added some significant enhancements >> since Apache Commons Build Plugin Maven Mojo 1.9 was released, so I would >> like to release Apache Commons Build Plugin Maven Mojo 1.10. >> >> Apache Commons Build Plugin Maven Mojo 1.10 RC2 is available for review >> here: >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2 >> (svn revision 32839) >> >> The Git tag commons-commons-build-plugin-1.10-RC2 commit for this RC is >> 5f477eeb76bfc16dd2d31f9b75bb9d6ebd7a1b52 which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-build-plugin.git;a=commit;h=5f477eeb76bfc16dd2d31f9b75bb9d6ebd7a1b52 >> >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git >> --branch commons-build-plugin-1.10-RC2 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1429/org/apache/commons/commons-build-plugin/1.10/ >> >> These are the Maven artifacts and their hashes in Nexus: >> >> #Nexus SHA-1s >> >> commons-build-plugin-1.10-test-sources.jar=97da2d6f0c62bf642b8b0cf9df6d61a5bdb62fc2 >> >> commons-build-plugin-1.10-tests.jar=b01907ddb6d583b09df81495acb5a3e2be0b9aad >> commons-build-plugin-1.10.pom=38dc8559c1bb27403dd890129d9b49a9c6029121 >> >> commons-build-plugin-1.10-javadoc.jar=e26f2a445e4a4f53af780a90387bf5db09b4490e >> >> commons-build-plugin-1.10-sources.jar=4abdf023528f9f0770d7354813685e7c683c8e3b >> commons-build-plugin-1.10.jar=f706a99f061f3049fd9407dc04e97ad5b1314df1 >> >> #Release SHA-512s >> #Sat Mar 09 16:48:03 EST 2019 >> >> commons-build-plugin-1.10-src-zip=79bd2b1dc5ba2cedb365d9ef796034b7a418ab4712aebb8ffd702f9619367c45c20bc436fca21b5aa9524568203af7962f6ecdb3a45fcfbc21c20c57291b06dd >> >> commons-build-plugin-1.10-src-tar.gz=0edb983308812b2bf94611086ba3585a4453ba10a03359bbaedd1a1e4233a8f066d849a51914b29e8332db8afc3e3eb5163d0bebeb65560f6ca439d01daa29fc >> >> >> >> I have tested this with 'mvn clean install site' using: >> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; >> 2018-10-24T14:41:47-04:00) >> Maven home: /usr/local/Cellar/maven/3.6.0/libexec >> Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: >> /Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home/jre >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "10.14.3", arch: "x86_64", family: "mac" >> >> >> Details of changes since 1.9 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/site >> (note some *relative* links are broken and the 1.10 directories are >> not yet created - these will be OK once the site is deployed.) >> >> CLIRR Report (compared to 1.9): >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/site/clirr-report.html >> >> JApiCmp Report (compared to 1.9): >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.10-RC2/site/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. >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but really should fix... >> [ ] -1 I oppose this release because... >> >> Thank you, >> >> Rob Tompkins, >> Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314) >> >> 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: >> >> git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git -b >> commons-commons-build-plugin-1.10-RC2 >> cd commons-commons-build-plugin-1.10-RC2 >> >> 2) Check Apache licenses: >> >> mvn apache-rat:check >> >> 3) Build the package: >> >> mvn -V clean package >> >> You can record the Maven and Java version produced by -V in your VOTE >> reply. >> >> 4) Build the site for a single module project: >> >> mvn site >> Check the site reports in: >> target\site\index.html >> >> 4) Build the site for a multi-module project: >> >> mvn site >> mvn site:stage >> Check the site reports in: >> target\site\index.html >> >> >> --------------------------------------------------------------------- >> 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
