+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 1:08 PM Gary Gregory <garydgreg...@gmail.com> wrote:

> Not a blocker: commons-codec 1.12 -> 1.13.
>
> Gary
>
> On Fri, Aug 30, 2019 at 10:10 AM Rob Tompkins <chtom...@gmail.com> wrote:
>
>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Release Plugin 1.6 was released, so I would like to
>> release Apache Commons Release Plugin 1.7.
>>
>> Apache Commons Release Plugin 1.7 RC1 is available for review here:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.7-RC1
>> (svn revision 35466)
>>
>> The Git tag commons-commons-release-plugin-1.7-RC1 commit for this RC is
>> 409d9525e05863415f91590192c544c6b9f7c2e9
>>
>> You may checkout this tag using:
>>     git clone
>> https://gitbox.apache.org/repos/asf/commons-commons-release-plugin.git
>> --branch commons-commons-release-plugin-1.7-RC1
>> commons-commons-release-plugin-1.7-RC1
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-release-plugin/1.7/
>>
>> These are the artifacts and their hashes:
>>
>> #Nexus SHA-1s
>>
>> commons-release-plugin-1.7-test-sources.jar=c888982e7ac0727530115cae4c3c2808cd59ef0e
>>
>> commons-release-plugin-1.7-tests.jar=2fdef721d93def37cb378b6ff3fcd4cb128b451c
>>
>> commons-release-plugin-1.7-sources.jar=f821c5d50124bd2228ad898ec2cb92c5034992f3
>> commons-release-plugin-1.7.jar=6ef41fc5ecebed5d201788e4e1411f431dfd58cb
>> commons-release-plugin-1.7.pom=57c311cd4b55d6c0f3eb3f33d02996c8ab6afaa0
>>
>> commons-release-plugin-1.7-javadoc.jar=59b86042e91701129571850bf2f7092efcbd35b2
>>
>> #Release SHA-512s
>> #Fri Aug 30 09:58:56 EDT 2019
>>
>> commons-release-plugin-1.7-bin.tar.gz=87517bbf53f15e5c4d0875cccc163da6427e3ae75a53545c4c706a6b978d4644e1b13b1145d402af9d4b69a559bc0d7efb6e673142edf158f73d10de22bc5c8f
>>
>> commons-release-plugin-1.7-bin.zip=63f49d533ba08629d2663ae8709fadd5fa76277c0c064f20c18e43921edfd05b03db7548bc30f66ac709d50f62ff23a7a45c6eaf655a96289fa509537f56db41
>>
>> commons-release-plugin-1.7-src.tar.gz=08de2f3b3b761073628bc18a1dee7b885c80d97ee53ddfd2eb1d00cf39198acad4219ae67cad88542e6ae0ebf2ebe36550c1dc0b5e1e8dca1b1031ddb918a42e
>>
>> commons-release-plugin-1.7-src.zip=88f5bd56dcd2b25d386f7f96b5042151374135eb39072960e6510234cd70a72230b3f39839bc971f20efa817acbfd7c64209cc246f81a0c1196660c37cfddaa3
>>
>> 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.6 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.7-RC1/RELEASE-NOTES.txt
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.7-RC1/site/changes-report.html
>>
>> Site:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.7-RC1/site/index.html
>>     (note some *relative* links are broken and the 1.7 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-release-plugin/1.7-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-release-plugin.git
>> --branch commons-commons-release-plugin-1.7-RC1
>> commons-commons-release-plugin-1.7-RC1
>> cd commons-commons-release-plugin-1.7-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
>>
>> -the end-
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>

Reply via email to