+1 >From the git tag. Apache RAT check OK.
I was able to do a local deployment with Apache Commons Text as a test using: mvn -V -Duser.name=%my_apache_id% -Dcommons.release-plugin.version=%commons.release-plugin.version% -Ddoclint=none -Prelease -Pjacoco -Ptest-deploy clean package site deploy Using: Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: C:\Java\apache-maven-3.6.1\bin\.. Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_221\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Gary On Fri, Aug 30, 2019 at 12:18 PM Rob Tompkins <chtom...@gmail.com> wrote: > Reasonable. I’ll sort that out when I update the site. > > -Rob > > > On Aug 30, 2019, at 12:14 PM, Gilles Sadowski <gillese...@gmail.com> > wrote: > > > > Hi. > > > > Documentation issue: see below. > > > >> Le ven. 30 août 2019 à 16:44, Rob Tompkins <chtom...@gmail.com> a > écrit : > >> > >> We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Build Plugin Maven Mojo 1.10 was released, so I would > like to release Apache Commons Build Plugin Maven Mojo 1.11. > >> > >> Apache Commons Build Plugin Maven Mojo 1.11 RC1 is available for review > here: > >> > https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.11-RC1 > (svn revision 35468) > >> > >> The Git tag commons-build-plugin-1.11-RC1 commit for this RC is > b67042233aef77f6f0599ef5a52982b3f0650978 > >> > >> You may checkout this tag using: > >> git clone > https://gitbox.apache.org/repos/asf/commons-build-plugin.git --branch > commons-build-plugin-1.11-RC1 commons-build-plugin-1.11-RC1 > >> > >> Maven artifacts are here: > >> > https://repository.apache.org/content/repositories/orgapachecommons-1461/org/apache/commons/commons-build-plugin/1.11/ > >> > >> These are the artifacts and their hashes: > >> > >> #Nexus SHA-1s > >> commons-build-plugin-1.11.jar=ea6c2ae38c032bdda39b2f8f760f973533be51d4 > >> commons-build-plugin-1.11.pom=fdace51c117a1136de14a7b659cf44a38740c8d5 > >> > commons-build-plugin-1.11-test-sources.jar=f5d3c86bc8af81afd471b0236a52e0282b4dde43 > >> > commons-build-plugin-1.11-javadoc.jar=fb92551a6a073dc17b0e88adb4b761c69207ec80 > >> > commons-build-plugin-1.11-sources.jar=1dd953b04d4a05ad4fc5c13fe025bbd8891f996a > >> > commons-build-plugin-1.11-tests.jar=9ba7961cf7c36e7bd4cac3ed53ff4fe15a09f133 > >> > >> > >> #Release SHA-512s > >> #Fri Aug 30 10:30:51 EDT 2019 > >> > commons-build-plugin-1.11-javadoc.jar=e749aae891d13af1c6dcea20e7386dbc6d9a7cbe56b0478c68ff210c713504ff7d144769d110a96881d695bc888d765958a17cf08d400a8988a8f4c6be9108c8 > >> > commons-build-plugin-1.11-sources.jar=1ef7d44774d5c83cdd74e3e069f738446f0e5e180d0a2ce73a5b5dbc71a5bc9f3119a44efc1e5340a5376ce0e77beeaa4e3baffac3a0dc154bc2ea57718899ed > >> > commons-build-plugin-1.11-src.tar.gz=1075448c49d5d2312d2ae9812f347600300e415f05d5b32ef2e261a7afcf10bf0733dffc8da13025e28cb58bce3cb22a98e24aeb6369cfb38f627cbf61f23c78 > >> > commons-build-plugin-1.11-src.zip=9f144ecbece6e3252bbc2d8a7a3d5c38ef02e9d2f159c77ab1e6a98d403a87f2b20fbb2b682771e6a5d863880c1f74448d205ced89080a17b37dfc7f9e5d02ed > >> > commons-build-plugin-1.11-test-sources.jar=b830741d3fbebf833b96a51c731c4c9be0f66b32c65a57ca583c6803fa7e522e6944c763bb6829d4350cc685b000655a09b6a58b6da16a65b633ddd32440b12a > >> > commons-build-plugin-1.11-tests.jar=83b368a69c0237099413931c8d38611ff20655d9db665891dd7d12c910e36223fa61d40232830ab04a2450d5950f8e70ceba7cea1a95b8adf0efcfc0b9757a3c > >> > >> > >> I have tested this with 'mvn clean install site' using: > >> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; > 2019-04-04T15:00:29-04:00) > >> Maven home: /usr/local/Cellar/maven/3.6.1/libexec > >> Java version: 1.8.0_202, vendor: Amazon.com Inc., runtime: > /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre > >> Default locale: en_US, platform encoding: UTF-8 > >> OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac" > >> > >> > >> Details of changes since 1.10 are in the release notes: > >> > https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.11-RC1/RELEASE-NOTES.txt > >> > https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.11-RC1/site/changes-report.html > >> > >> Site: > >> > https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.11-RC1/site/index.html > >> (note some *relative* links are broken and the 1.11 directories are > not yet created - these will be OK once the site is deployed.) > >> > >> RAT Report: > >> > https://dist.apache.org/repos/dist/dev/commons/commons-build-plugin/1.11-RC1/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 tag > >> > >> git clone > https://gitbox.apache.org/repos/asf/commons-commons-build-plugin.git > --branch commons-commons-build-plugin-1.11-RC1 > commons-commons-build-plugin-1.11-RC1 > >> cd commons-commons-build-plugin-1.11-RC1 > >> > >> 2) Check Apache licenses > >> > >> This step is not required if the site includes a RAT report page which > you then must check. > >> > >> mvn apache-rat:check > >> > >> 3) Check binary compatibility > >> > >> Older components still use Apache Clirr: > >> > >> This step is not required if the site includes a Clirr report page > which you then must check. > >> > >> mvn clirr:check > >> > >> Newer components use JApiCmp with the japicmp Maven Profile: > >> > >> This step is not required if the site includes a JApiCmp report page > which you then must check. > >> > >> mvn install -DskipTests -P japicmp japicmp:cmp > >> > >> 4) Build the package > >> > >> mvn -V clean package > >> > >> You can record the Maven and Java version produced by -V in your VOTE > reply. > >> To gather OS information from a command line: > >> Windows: ver > >> Linux: uname -a > >> > >> 5) Build the site for a single module project > >> > >> Note: Some plugins require the components to be installed instead of > packaged. > >> > >> mvn site > >> Check the site reports in: > >> - Windows: target\site\index.html > >> - Linux: target/site/index.html > >> > >> 6) Build the site for a multi-module project > >> > >> mvn site > >> mvn site:stage > >> Check the site reports in: > >> - Windows: target\site\index.html > >> - Linux: target/site/index.html > > > > That should be > > ---CUT--- > > target/staging/index.html > > ---CUT--- > > > > Regards, > > Gilles > > > >> > >> -the end- > > > > --------------------------------------------------------------------- > > 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 > >
