Re: [VOTE] Redirect github notifications to issues@

[Rob Tompkins]

Many thanks.

> On Mar 4, 2019, at 12:25 PM, Marcelo Vanzin  
> wrote:
> 
> FYI, it should all be done now, so if you want to get notifications,
> either sign up to issues@, or watch the repo on github.
> 
> On Fri, Feb 22, 2019 at 9:49 AM Marcelo Vanzin  wrote:
>> 
>> Jira link: https://issues.apache.org/jira/browse/INFRA-17892
>> 
>> On Fri, Feb 22, 2019 at 9:44 AM Marcelo Vanzin  wrote:
>>> 
>>> Thanks all, vote passes with 11 +1s, no -1s.
>>> 
>>> I'll file the INFRA ticket and link it back here soon.
>>> 
>>> On Tue, Feb 19, 2019 at 1:35 PM Marcelo Vanzin  wrote:
 
 I'm opening a vote based on recent discussions about the extra noise
 generated by github updates going to dev@. So please vote:
 
 - +1 to redirect github updates of all commons repos to the issues@ list
 - -1 to keep things as is
 
 If the vote passes, I'll take care of opening an infra ticket
 referencing the result.
 
 --
 Marcelo
>>> 
>>> 
>>> 
>>> --
>>> Marcelo
>> 
>> 
>> 
>> --
>> Marcelo
> 
> 
> 
> -- 
> Marcelo
> 
> -
> 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

[text] Going to use staging area for testing release-plugin

[Rob Tompkins]

Hello all,

I’m fiddling around with the release plugin and I’m going to commit some files 
to the [text] staging area for the sake of testing a maven mojo that cleans up 
the staging area. Just wanted to give everyone a heads up.

-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [DRAFT][REPORT] Board report for March 2019

[Rob Tompkins]

Looks reasonable to me.
-Rob

> On Mar 6, 2019, at 8:28 AM, Gary Gregory  wrote:
> 
> All feedback welcome.
> --
> ## Description:
> - Apache Commons is an Apache project focused on all aspects of reusable
> Java
>   components.
> 
> ## Issues:
> - There are no issues requiring board attention at this time.
> 
> ## Activity:
> - Activity is good with the release of 9 components.
> 
> ## Health report:
> - We migrated all active components that remained in Subversion to GitBox.
> - The project is healthy and has weclomed a new committer.
> - We are continuing to imporove the release process by updating our Maven
> plugins.
> - Mailing activity is good and JIRAs are addressed in a timely manner for
> most components.
> 
> ## PMC changes:
> 
> - Currently 38 PMC members.
> - No new PMC members added in the last 3 months
> - Last PMC addition was Rob Tompkins on Fri Jun 30 2017
> 
> ## Committer base changes:
> 
> - Currently 147 committers.
> - Maxim Solodovnik was added as a committer on Tue Dec 18 2018
> 
> ## Releases:
> 
> - BCEL-6.3 was released on Sun Jan 27 2019
> - CODEC-1.12 was released on Tue Feb 12 2019
> - COLLECTIONS-4.3 was released on Mon Feb 04 2019
> - DBCP-2.6.0 was released on Tue Feb 19 2019
> - FILEUPLOAD-1.4 was released on Thu Dec 27 2018
> - POOL-2.6.1 was released on Tue Feb 12 2019
> - RELEASE-PLUGIN-1.5 was released on Tue Jan 29 2019
> - RNG-1.2 was released on Tue Dec 11 2018
> - VFS-2.3 was released on Sun Feb 03 2019
> 
> ## JIRA activity:
> 
> - 138 JIRA tickets created in the last 3 months
> - 100 JIRA tickets closed/resolved in the last 3 months
> 
> Gary Gregory
> Your Apache Commons Chair


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Google Summer of Code 2019 Mentor Registration

[Rob Tompkins]

How much work is it? I’ve not done it before, but I’d be happy to consider it.

-Rob

> On Mar 8, 2019, at 3:14 PM, Gilles Sadowski  wrote:
> 
> Hi.
> 
> Anyone willing to apply (cf. message below)?
> 
> Regards,
> Gilles
> 
> -- Forwarded message -
> From: Ulrich Stärk mailto:u...@apache.org>>
> Date: ven. 8 mars 2019 à 20:49
> Subject: Google Summer of Code 2019 Mentor Registration
> To: mailto:ment...@community.apache.org>>
> Cc: d...@community.apache.org  
> mailto:d...@community.apache.org>>
> 
> 
> Dear PMCs,
> 
> I'm happy to announce that the ASF has made it onto the list of
> accepted organizations for
> Google Summer of Code 2019! [1,2]
> 
> It is now time for mentors to sign up, so please pass this email on to
> your community and
> podlings. If you aren’t already subscribed to
> ment...@community.apache.org you should do so now else
> you might miss important information.
> 
> Mentor signup requires two steps: mentor signup in Google's system [3]
> and PMC acknowledgement.
> 
> If you want to mentor a project in this year's SoC you will have to
> 
> 1. Be an Apache committer.
> 2. Request an acknowledgement from the PMC for which you want to
> mentor projects. Use the below
> template and *do not forget to copy ment...@community.apache.org*. We
> will use the email adress you
> indicate to send the invite to be a mentor for Apache.
> 
> PMCs, read carefully please.
> 
> We request that each mentor is acknowledged by a PMC member. This is
> to ensure the mentor is in good
> standing with the community. When you receive a request for
> acknowledgement, please ACK it and cc
> ment...@community.apache.org
> 
> Lastly, it is not yet too late to record your ideas in Jira (see
> previous emails for details).
> Students will now begin to explore ideas so if you haven’t already
> done so, record your ideas
> immediately!
> 
> Cheers,
> 
> The Apache GSoC Team
> 
> mentor request email template:
> 
> to: private@.apache.org
> cc: ment...@community.apache.org
> subject: GSoC 2019 mentor request for 
> 
>  PMC,
> 
> please acknowledge my request to become a mentor for Google Summer of
> Code 2018 projects for Apache
> .
> 
> I would like to receive the mentor invite to 
> 
> 
> 
> 
> 
> [1] https://summerofcode.withgoogle.com/organizations/
> [2] https://summerofcode.withgoogle.com/organizations/6614885824200704/
> [3] https://summerofcode.withgoogle.com/
> 
> -
> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org 
> 
> For additional commands, e-mail: private-h...@commons.apache.org 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> 
> For additional commands, e-mail: dev-h...@commons.apache.org 
> 

[LAZY][VOTE] Release Apache Commons Release Plugin 1.6 based on RC1

[Rob Tompkins]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons Release Plugin 1.5 was released, so I would like to release 
Apache Commons Release Plugin 1.6.

Apache Commons Release Plugin 1.6 RC1 is available for review here:

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1 
(svn revision 32834)

The Git tag commons-release-plugin-1.6-RC1 commit for this RC is 
201c6ff24ca85355ece3574f788eca250c03b241 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=201c6ff24ca85355ece3574f788eca250c03b241

You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git 
--branch commons-release-plugin-1.6-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1428/org/apache/commons/commons-release-plugin/1.6/

These are the Maven artifacts and their hashes in Nexus:

#Nexus SHA-1s
commons-release-plugin-1.6.jar=0c8be1cc9389e0ad195b8855a59661f213ad9c66
commons-release-plugin-1.6-javadoc.jar=4d0b85d9eb8faaecc9dca066efedc4a303fe250f
commons-release-plugin-1.6-sources.jar=2d9cfde308c8dbef123d63a45d37279ac7616ff4
commons-release-plugin-1.6-test-sources.jar=649544ee37192d4519b4a189a4af4c1cdc9feba3
commons-release-plugin-1.6.pom=cfb03fad4ce8ab87f0224034840fa3f1659eb32e
commons-release-plugin-1.6-tests.jar=a906c3436fd328a5d2b973105a507a33d29eb07c

#Release SHA-512s
#Sat Mar 09 08:30:24 EST 2019
commons-release-plugin-1.6-bin-tar.gz=90734778b0af8acaf1ab84d5c97e3c01d12f95d2a720f990d03aa17b9b34ea2facf5fb884dbe7cde66f4ff93dc3e37b6119e2c5e43bc60f2e87bad62913c371b
commons-release-plugin-1.6-src-zip=f0d35d9c4b4edf6192600346e3a7c5f90c663839c634bf31a2c6eea57fddf1bd84a966e47f30fb44de04a2a009d3bee613c2bd41268305bc5e45d1769dbe4a9b
commons-release-plugin-1.6-src-tar.gz=d7b0a17927583afdbd45d21a2abf6a066502995087e59c0498eca03a51d2e30ab4b89f2590d09f7b3144231eabdf583822a5802a6f0d1b4cc4b2a201df15665b
commons-release-plugin-1.6-bin-zip=b36fd453f5a73a6295c38e9896dd958390f21570595eeb0863fe64f9f27ec0f0dfde488e755bd7fa220f1e54c1af772399f3c006e1c92b7082c605223657cfa9


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.5 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site
(note some *relative* links are broken and the 1.6 directories are not yet 
created - these will be OK once the site is deployed.)

CLIRR Report (compared to 1.5):

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/clirr-report.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-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:

git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git -b 
commons-release-plugin-1.6-RC1
cd commons-release-plugin-1.6-RC1

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

Re: [apache/commons-text] TEXT-155: Add a generic IntersectionSimilarity measure (#109)

[Rob Tompkins]

We should be a tad careful with our naming conventions here. In the 
combinatorics on words space, an “overlap” is a specific repeated pattern, 
namely cXcXc where c is a letter from an alphabet and X is string (allowed to 
be empty).

> On Mar 9, 2019, at 4:19 PM, Alex Herbert  wrote:
> 
> @aherbert  pushed 1 commit.
> 
> 9a7d018 
> 
>  TEXT-155: Renamed to OverlapSimilarity.
> —
> You are receiving this because you are subscribed to this thread.
> View it on GitHub 
> 
>  or mute the thread 
> .
> 

Re: [apache/commons-text] TEXT-155: Add a generic IntersectionSimilarity measure (#109)

[Rob Tompkins]

Also this breaks binary compatibility. Are we going for a 2.X with [text]?

> On Mar 9, 2019, at 5:01 PM, Rob Tompkins  wrote:
> 
> We should be a tad careful with our naming conventions here. In the 
> combinatorics on words space, an “overlap” is a specific repeated pattern, 
> namely cXcXc where c is a letter from an alphabet and X is string (allowed to 
> be empty).
> 
>> On Mar 9, 2019, at 4:19 PM, Alex Herbert > <mailto:notificati...@github.com>> wrote:
>> 
>> @aherbert <https://github.com/aherbert> pushed 1 commit.
>> 
>> 9a7d018 
>> <https://github.com/apache/commons-text/commit/9a7d018c3e85031749166195ebab66c07b7d94c6>
>>  TEXT-155: Renamed to OverlapSimilarity.
>> —
>> You are receiving this because you are subscribed to this thread.
>> View it on GitHub 
>> <https://github.com/apache/commons-text/pull/109/files/ae21c63dcb7f57893d095c802c596b7db268d673..9a7d018c3e85031749166195ebab66c07b7d94c6>
>>  or mute the thread 
>> <https://github.com/notifications/unsubscribe-auth/ABO1E9AVw6sBj3vetbCaXoC7F8QHT8Bmks5vVCV5gaJpZM4bjORj>.
>> 
> 

Re: [Parent] RAT check

[Rob Tompkins]

> On Mar 9, 2019, at 7:40 PM, Gilles Sadowski  wrote:
> 
>> Le sam. 9 mars 2019 à 23:45, Gary Gregory  a écrit :
>> 
>> Hi all:
>> 
>> How about making apache-rat:check run automatically in commons-parent? In
>> the Maven validate phase?
>> 
>> That would mean one less thing to check when integrating a patch and
>> validating an RC.
> 
> +1
> [Why not?]
> 

Agree +1


> Gilles
> 
> 
>> 
>> Gary
> 
> -
> 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

[all] GitHub Release Notes

[Rob Tompkins]

Now that we have gitbox enabled, committers can “draft releases” in github 
which includes the ability to upload artifacts and add release notes to tags. 
I’ll give an example of what’s possible with the upcoming release of the 
[commons-release-plugin]. At $work I’ve been using this functionality for quite 
some time and have found it convenient.

Figured I’d let folks know about it. As it could be a user friendly item. 
Obviously we would not want to put anything in the releases area that we are 
not keeping direct track of in Apache infrastructure.

Cheers,
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

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

Re: [release][build] Merge plugins?

[Rob Tompkins]

+1 Will do this after getting parent v48 out.

> On Mar 10, 2019, at 1:58 PM, Gary Gregory  wrote:
> 
> Hi All:
> 
> Should we merge our internal release and build Maven plugins?
> 
> Gary


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

This should be fixed, and the git hashes should remain unchanged.

-ROb

> On Mar 11, 2019, at 12:54 PM, Rob Tompkins  wrote:
> 
> 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  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  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

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

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  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  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)
>>

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

> On Mar 11, 2019, at 12:59 PM, Gary Gregory  wrote:
> 
> Thanks ROb, the command 'git clone

not a problem

-ROb :-P

> https://gitbox.apache.org/repos/asf/commons-build-plugin.git --branch
> commons-build-plugin-1.10-RC2' now succeeds.
> 
> Gary
> 
> On Mon, Mar 11, 2019 at 12:58 PM Rob Tompkins  wrote:
> 
>> This should be fixed, and the git hashes should remain unchanged.
>> 
>> -ROb
>> 
>>> On Mar 11, 2019, at 12:54 PM, Rob Tompkins  wrote:
>>> 
>>> 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 
>> 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  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"
>>>>> 
>>>>> 

Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.6 based on RC1

[Rob Tompkins]

Here’s my +1 for this release.

> On Mar 9, 2019, at 8:53 AM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Release Plugin 1.5 was released, so I would like to release 
> Apache Commons Release Plugin 1.6.
> 
> Apache Commons Release Plugin 1.6 RC1 is available for review here:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1 
> (svn revision 32834)
> 
> The Git tag commons-release-plugin-1.6-RC1 commit for this RC is 
> 201c6ff24ca85355ece3574f788eca250c03b241 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=201c6ff24ca85355ece3574f788eca250c03b241
> 
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git 
> --branch commons-release-plugin-1.6-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1428/org/apache/commons/commons-release-plugin/1.6/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus SHA-1s
> commons-release-plugin-1.6.jar=0c8be1cc9389e0ad195b8855a59661f213ad9c66
> commons-release-plugin-1.6-javadoc.jar=4d0b85d9eb8faaecc9dca066efedc4a303fe250f
> commons-release-plugin-1.6-sources.jar=2d9cfde308c8dbef123d63a45d37279ac7616ff4
> commons-release-plugin-1.6-test-sources.jar=649544ee37192d4519b4a189a4af4c1cdc9feba3
> commons-release-plugin-1.6.pom=cfb03fad4ce8ab87f0224034840fa3f1659eb32e
> commons-release-plugin-1.6-tests.jar=a906c3436fd328a5d2b973105a507a33d29eb07c
> 
> #Release SHA-512s
> #Sat Mar 09 08:30:24 EST 2019
> commons-release-plugin-1.6-bin-tar.gz=90734778b0af8acaf1ab84d5c97e3c01d12f95d2a720f990d03aa17b9b34ea2facf5fb884dbe7cde66f4ff93dc3e37b6119e2c5e43bc60f2e87bad62913c371b
> commons-release-plugin-1.6-src-zip=f0d35d9c4b4edf6192600346e3a7c5f90c663839c634bf31a2c6eea57fddf1bd84a966e47f30fb44de04a2a009d3bee613c2bd41268305bc5e45d1769dbe4a9b
> commons-release-plugin-1.6-src-tar.gz=d7b0a17927583afdbd45d21a2abf6a066502995087e59c0498eca03a51d2e30ab4b89f2590d09f7b3144231eabdf583822a5802a6f0d1b4cc4b2a201df15665b
> commons-release-plugin-1.6-bin-zip=b36fd453f5a73a6295c38e9896dd958390f21570595eeb0863fe64f9f27ec0f0dfde488e755bd7fa220f1e54c1af772399f3c006e1c92b7082c605223657cfa9
> 
> 
> 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.5 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site
>(note some *relative* links are broken and the 1.6 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 1.5):
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/clirr-report.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-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:
> 
> git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git -b 
> commons-release-plugin-1.6-RC1
> cd commons-release-plugin-1.6-RC1
> 
> 2) Check Apache licenses:
> 
> mvn apache-rat:check
> 
> 3) Bu

[RESULT][LAZY][VOTE] Release Apache Commons Release Plugin 1.6 based on RC1

[Rob Tompkins]

With the following votes:

Gary Gregory: +1, and
Rob Tompkins: +1;

this [LAZY][VOTE] passes. I will go ahead and perform the release process.

-Rob

> On Mar 9, 2019, at 8:53 AM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Release Plugin 1.5 was released, so I would like to release 
> Apache Commons Release Plugin 1.6.
> 
> Apache Commons Release Plugin 1.6 RC1 is available for review here:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1 
> (svn revision 32834)
> 
> The Git tag commons-release-plugin-1.6-RC1 commit for this RC is 
> 201c6ff24ca85355ece3574f788eca250c03b241 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=201c6ff24ca85355ece3574f788eca250c03b241
> 
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git 
> --branch commons-release-plugin-1.6-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1428/org/apache/commons/commons-release-plugin/1.6/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus SHA-1s
> commons-release-plugin-1.6.jar=0c8be1cc9389e0ad195b8855a59661f213ad9c66
> commons-release-plugin-1.6-javadoc.jar=4d0b85d9eb8faaecc9dca066efedc4a303fe250f
> commons-release-plugin-1.6-sources.jar=2d9cfde308c8dbef123d63a45d37279ac7616ff4
> commons-release-plugin-1.6-test-sources.jar=649544ee37192d4519b4a189a4af4c1cdc9feba3
> commons-release-plugin-1.6.pom=cfb03fad4ce8ab87f0224034840fa3f1659eb32e
> commons-release-plugin-1.6-tests.jar=a906c3436fd328a5d2b973105a507a33d29eb07c
> 
> #Release SHA-512s
> #Sat Mar 09 08:30:24 EST 2019
> commons-release-plugin-1.6-bin-tar.gz=90734778b0af8acaf1ab84d5c97e3c01d12f95d2a720f990d03aa17b9b34ea2facf5fb884dbe7cde66f4ff93dc3e37b6119e2c5e43bc60f2e87bad62913c371b
> commons-release-plugin-1.6-src-zip=f0d35d9c4b4edf6192600346e3a7c5f90c663839c634bf31a2c6eea57fddf1bd84a966e47f30fb44de04a2a009d3bee613c2bd41268305bc5e45d1769dbe4a9b
> commons-release-plugin-1.6-src-tar.gz=d7b0a17927583afdbd45d21a2abf6a066502995087e59c0498eca03a51d2e30ab4b89f2590d09f7b3144231eabdf583822a5802a6f0d1b4cc4b2a201df15665b
> commons-release-plugin-1.6-bin-zip=b36fd453f5a73a6295c38e9896dd958390f21570595eeb0863fe64f9f27ec0f0dfde488e755bd7fa220f1e54c1af772399f3c006e1c92b7082c605223657cfa9
> 
> 
> 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.5 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site
>(note some *relative* links are broken and the 1.6 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 1.5):
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-RC1/site/clirr-report.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.6-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:
> 
> git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git -b 
> commons-release-plugin-1.6-RC1
> cd commons-release-plugin-1.6-RC1
> 
> 2) Check Apache lice

[all] Should we use MathJaX in Javadoc on all repos? (Was: Re: [jira] [Commented] (NUMBERS-58) Javadoc: Use MathJaX)

[Rob Tompkins]

For those unfamiliar with MathJaX, is the javascript mechanism for 
accommodating for LaTeX (the math typesetting language, written by Donald 
Knuth) in html. 

It could be convenient to use mathematical notation in our javadoc generally. 
That said, Java doesn’t do this so it would indeed be non-standard. My opinion 
is in the +0.5 zone currently.

Thoughts?

-Rob

> On Mar 12, 2019, at 8:15 AM, Alex D Herbert (JIRA)  wrote:
> 
> 
>[ 
> https://issues.apache.org/jira/browse/NUMBERS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790478#comment-16790478
>  ] 
> 
> Alex D Herbert commented on NUMBERS-58:
> ---
> 
> I fixed math and statistics when I fixed Rng. However the fix is not present 
> in numbers.
> 
> The fix is to swap the  `` tag for `` in 
> the `maven-javadoc-plugin` configuration.
> 
> It requires maven-javadoc-plugin version 3, which the new pom does have so 
> the fix is applicable.
> 
> 
> 
> 
> 
> 
> 
> 
>> Javadoc: Use MathJaX
>> 
>> 
>>Key: NUMBERS-58
>>URL: https://issues.apache.org/jira/browse/NUMBERS-58
>>Project: Commons Numbers
>> Issue Type: Task
>> Components: complex
>>   Reporter: Gilles
>>   Priority: Minor
>> Labels: javadoc
>> 
>> Using MathJaX would make both reading the generated "apidocs" and reading 
>> the Javadoc from the source files a more pleasant experience.
>> Unfortunately, the generated web site fails to load the MathJax interpreter 
>> (see discussion in COMMONSSITE-100).
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GSoC] Example Issues From 2018 or upcoming 2019

[Rob Tompkins]

Hey guys (or maybe Gilles specifically),

It looks like a good example for GSoC jira issues is: 
https://issues.apache.org/jira/browse/RNG-32 
. Are there other examples? And 
when are we “supposed” to have our issues reasonably labeled by?

-Rob

[ANNOUNCE] Commons Release Plugin 1.6 released.

[Rob Tompkins]

[This announcement is only going to the dev list.]

The Apache Commons Release Plugin team is pleased to announce the release of 
Apache
Commons Release Plugin 1.6.

The Apache Commons Release Plugin is a collection of Java based Maven mojos for
Apache Commons
Release process. These mojos are intended to be used as a collection of steps to
be strung
together for the purpose of removing the manual steps required to produce an
Apache Commons Release.

List of changes:
http://commons.apache.org/commons-release-plugin/changes-report.html

For complete information on Apache Commons Release Plugin, including
instructions
on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons
Release Plugin website:

http://commons.apache.org/commons-release-plugin/index.html

Cheers,
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

Here’s my +1.

> On Mar 9, 2019, at 8:33 PM, Rob Tompkins  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

[RESULT][LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.10 based on RC2

[Rob Tompkins]

This vote passes with the following votes:

Gary Gregory: +1,
Rob Tompkins: +1, and

no -1 votes. I will proceed with promoting the release.

All the best,
-Rob

> On Mar 9, 2019, at 8:33 PM, Rob Tompkins  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 

Re: [ANNOUNCE] Commons Release Plugin 1.6 released.

[Rob Tompkins]

No worries. The main way to run things when you do a promotion is:

mvn -Duser.name= -Prelease clean commons-release:clean-staging 
test package site deploy

or for dry run:

mvn -Duser.name= -Prelease -Ptest-deploy clean 
commons-release:clean-staging test package site deploy

doing this should clean up the dist.apache.org <http://dist.apache.org/> dev 
staging directory if there’s anything there when you start the staging process.

-Rob

> On Mar 13, 2019, at 9:20 PM, Bruno P. Kinoshita  wrote:
> 
> Was waiting for the release before start working on imaging RC3.
> Thanks Rob!
> Bruno
> 
> 
>On Thursday, 14 March 2019, 2:17:43 pm NZDT, Rob Tompkins 
>  wrote:  
> 
> [This announcement is only going to the dev list.]
> 
> The Apache Commons Release Plugin team is pleased to announce the release of 
> Apache
> Commons Release Plugin 1.6.
> 
> The Apache Commons Release Plugin is a collection of Java based Maven mojos 
> for
> Apache Commons
> Release process. These mojos are intended to be used as a collection of steps 
> to
> be strung
> together for the purpose of removing the manual steps required to produce an
> Apache Commons Release.
> 
> List of changes:
> http://commons.apache.org/commons-release-plugin/changes-report.html
> 
> For complete information on Apache Commons Release Plugin, including
> instructions
> on how to submit bug reports,
> patches, or suggestions for improvement, see the Apache Apache Commons
> Release Plugin website:
> 
> http://commons.apache.org/commons-release-plugin/index.html
> 
> Cheers,
> -Rob
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org

[ANNOUNCE] Apache Commons Build Plugin 1.10 Released

[Rob Tompkins]

[Not cross posted to @announce since this is internal to Commons]

Apache Commons has released the Apache Commons Build Plugin 1.10.

The Apache Commons Build Plugin is a Maven Plugin which can be used by
Apache Commons components.

See:
   http://commons.apache.org/commons-build-plugin/

VERSION 1.10 - 2019-02-26
-

Changes since the last release:
1. Use SHA512 signatures as the default in the download page. (update; ggregory)
2. Use SHA256 signatures as the default in the download page. (update; sebb)

Cheers,
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all] GitHub Release Notes

[Rob Tompkins]

> On Mar 15, 2019, at 1:05 PM, Matt Sicker  wrote:
> 
> Isn't there a related convo at the Incubator about that?

I’m not on at the incubatorguess I should subscribe. But wait...didn’t you 
tell me to do something like that some where else like a month ago :-P

-Rob

> 
> Anyways, this would be a neat feature for adding mirrors of official
> releases. The automatic releases feature for when you make a git tag
> can look weird, though, since they're not the actual release
> typically.
> 
>> On Sat, 9 Mar 2019 at 19:16, Rob Tompkins  wrote:
>> 
>> Now that we have gitbox enabled, committers can “draft releases” in github 
>> which includes the ability to upload artifacts and add release notes to 
>> tags. I’ll give an example of what’s possible with the upcoming release of 
>> the [commons-release-plugin]. At $work I’ve been using this functionality 
>> for quite some time and have found it convenient.
>> 
>> Figured I’d let folks know about it. As it could be a user friendly item. 
>> Obviously we would not want to put anything in the releases area that we are 
>> not keeping direct track of in Apache infrastructure.
>> 
>> Cheers,
>> -Rob
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 
> 
> -- 
> Matt Sicker 
> 
> -
> 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

[LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons Parent 47 was released, so I would like to release Apache 
Commons Parent 48.

Apache Commons Parent 48 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1 (svn 
revision 33098)


The Git tag commons-parent-48-RC1 commit for this RC is 
f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162

You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git --branch 
commons-parent-48-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/

These are the Maven artifacts:

#Release SHA-512s
#Wed Mar 20 11:07:15 EDT 2019
commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
commons-parent-48-src-tar.gz=b52eb5416ad28356ac24b54fb6ee831919584606f71f99cd7cfc7bd00e92fd40ae1e838bb9d7a6f2914d777313b0c7682fbbe6a158845be3461f75d9c120cfd4



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 47 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site
(note some *relative* links are broken and the 48 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-parent/48-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:

git clone https://gitbox.apache.org/repos/asf/commons-parent.git -b 
commons-parent-48-RC1
cd commons-parent-48-RC1

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

[all] What versions of java do we support?

[Rob Tompkins]

Hello all,

I would think that with the Amazon Corretto play at long term support for java 
8 and 11 we would want to build using the latest version of the Corretto 8-JDK, 
and we would want to ensure that we work for Java 11. Regarding later versions 
of Java I’m a tad agnostic currently as we are less certain with their 
stability.

What are folks’ thoughts?

-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons BCEL 6.3.1 based on RC1

[Rob Tompkins]

+1, build works on java 8 and 10, site good, signatures good, rat good..some 
nits low coverage and we could improve the checkstyle/pmd and such.

> On Mar 21, 2019, at 4:07 AM, Bruno P. Kinoshita 
>  wrote:
> 
>   [ X ] +1 Release these artifacts
> 
> 
> Build passing with `mvn clean test install site` on
> 
> 
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-18T06:33:14+12:00)Maven home: /opt/apache-maven-3.5.4Java version: 
> 1.8.0_191, vendor: Oracle Corporation, runtime: 
> /usr/lib/jvm/java-8-openjdk-amd64/jreDefault locale: en_NZ, platform 
> encoding: UTF-8
> OS name: "linux", version: "4.15.0-46-generic", arch: "amd64", family: "unix"
> 
> 
> Fails on javadocs when using JVM 10, and fails almost immediately using JVM 
> 11. But I assume this is not a blocker.
> 
> 
> Reports, including Clirr, look OK too. Checked changes report and had a brief 
> look at the pull requests changes. All looking OK.
> 
> 
> Checked signatures of dist area binaries and sources, and maven staged 
> artefacts. Look OK too.
> 
> 
> Cheers
> Bruno
> 
> 
> 
> 
> 
> 
> 
> On Thursday, 21 March 2019, 3:27:06 pm NZDT, Gary Gregory 
>  wrote: 
> 
> 
> 
> 
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons BCEL 6.3 was released, so I would like to release
> Apache Commons BCEL 6.3.1.
> 
> Apache Commons BCEL 6.3.1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.3.1-RC1 (svn
> revision 33105)
> 
> The Git tag commons-bcel-6.3.1-RC1 commit for this RC is
> 9174edf0d530540c9f6df76b4d786c5a6ad78a5d which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=9174edf0d530540c9f6df76b4d786c5a6ad78a5d
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-bcel.git --branch
> commons-bcel-6.3.1-RC1
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1431/org/apache/bcel/bcel/6.3.1/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Release SHA-512s
> #Wed Mar 20 22:06:36 EDT 2019
> bcel-6.3.1-test-sources-jar.asc=9d4193586ae639324235ad395fa9823e4a447ffae5fc5eea1daba183a1a5d357879803f6cad1279559c127e36a2bf9d55dd69145c6504906629c6d1214e7552b
> bcel-6.3.1-bin-zip=46d40f897391cee2f1166a195e512d700524ce25ef3af2c1ccff7f540047000848873c9536c5feb2743aaf34826824e1a80bccf2e386f9c0de4af5fc66214511
> bcel-6.3.1-tests-test-jar=4d230f77af84feb78467ab607363efd7de5ef70afc0e8d66c3c77ed2018c7925520d68cce2b2adaff96794d68a97292a565c2681b984a8de3629af7605827ddf
> bcel-6.3.1-javadoc-javadoc=36f8246b07bb6b13bcdf715ca29998624a6faf78dff270cbbf09dfa2214793c35202ae0ea213eaeb38dcd1f8c297896f00ea5c03e967f721f1fbba8a3829c630
> bcel-6.3.1-bin-zip.asc=ff67061e5050a100b30d70a46eb870b0684acf4e8ed163eea51593b55dd6fc9646272d2efb806c2d19fd8b9cb5100c36ef002c18d1de91d3255644ca4f5f59f0
> bcel-6.3.1-src-tar.gz=4e601b054b003c2077fa00152020e36dc41e216172c8f3075e8ac63e2c6f4b0334a8ab5b075b53fa0b7e64c0c8fd9cd14a28617790f556467bd38182c6c6cbfd
> bcel-6.3.1-bin-tar.gz.asc=694a8b63dbe06460eb18429a2a3cc60b67a3841e92341770ed239b757b925ab23b4d429ebca45979e629a102b9614e9c774644d82a63430f8ecdd305bb600a91
> bcel-6.3.1-pom.asc=7c8215ff0b054ee445795fb05800fdb534b93fdb6565b3b99bb8913b8359e7746b6ed2195861dc899c41699d4362b28f6dd22c1e3046080db612d53876da89cd
> bcel-6.3.1-tests-jar.asc=2cb1a700668d2a587d533cc824b836acff6152ab7f47d74b0b406468f95f1684c0cd1162dfdc9649d9b1f609ca31af76959aa43caffd6f84ad67fa103d001110
> bcel-6.3.1-sources-jar.asc=2a654a56f184be2ed06ba2909715ae50bdc69e7fe19153d0df98d68aa39a73f6560fab9e60f3e6b076240853b0f6b2fcf60e375aa0db328c3889dc921fa67674
> bcel-6.3.1-bin-tar.gz=eef969730f189d2e43ce77bee89123fad84f203145e76fe20a38b5748dfc6c878bb98a7365466408258ebca922913dcbb9802e4dc59db8c928f2b18a68bf0584
> bcel-6.3.1-src-tar.gz.asc=cd99a46410311577869242dc78eb55cbbf43701e1dda88b80e838e95e4a769eb93c123dc9083a4dc2c3db08822add420b97c3c4586448db3e357aa8a3aebefdd
> bcel-6.3.1-test-sources-java-source=74598336729ef45bce7c2cd04c25f3a30a898702c86308f0bf0557ff39f0368f3b821b86f0df5bb4df56083389c033aed3dc78402c81ea0a837ecc9c9b505846
> bcel-6.3.1-src-zip.asc=bf45f2a52dfe27875de726095e769ebda68be37408ff2a92410fd0314f023637f222b7febeccf04d92024ccf8fed177ebc3aafd2b4579536c679593bdf665abd
> bcel-6.3.1-javadoc-jar.asc=8646dfbe7dc86bad659f89a9772f862df5026f9338a0a03291abc6ed7a79758b91f89dcae310c3d81d8cc935838b9c29d1b89f1d72b8556ca40e9dbccbd837cd
> bcel-6.3.1-sources-java-source=75a548736f9a9ece49e994bdd6b2e26588ddc6ca4d45a04dc2ebe2058080aea95b15c2eadb88caf743d35aaf2025a49a085bd391b7099dc4b832fd479ffd816d
> bcel-6.3.1-src-zip=d0e98d097437c7d40b863403a8a05c6c5eaa2afea121a312f072ecf5775b8b3e12441c1d7db6ce91eb45fbb583643c5189bc8eace38e610f26dc074fa9247776
> bcel-6.3.1-jar.asc=be630ac3f294b0a3eb77ad8f5ed3408bc5d8985c21785654e5f1f43137ed86b5febc3bf45fd986d8f2d35e3c2d9bbedfc33003b408a583fa18d583d15b86a871
> 
> 
> (no need for .asc hashes!)
> 
> I h

Re: [all] What versions of java do we support?

[Rob Tompkins]

Is there LTS with those other imolementations?

> On Mar 21, 2019, at 9:43 PM, Ralph Goers  wrote:
> 
> Why are you singling out Corretto? What about AdoptOpenJDK or RedHat’s 
> OpenJDK support? The ASF is supposed to be vendor neutral.
> 
> Ralph
> 
>> On Mar 21, 2019, at 11:05 AM, Rob Tompkins  wrote:
>> 
>> Hello all,
>> 
>> I would think that with the Amazon Corretto play at long term support for 
>> java 8 and 11 we would want to build using the latest version of the 
>> Corretto 8-JDK, and we would want to ensure that we work for Java 11. 
>> Regarding later versions of Java I’m a tad agnostic currently as we are less 
>> certain with their stability.
>> 
>> What are folks’ thoughts?
>> 
>> -Rob
>> -
>> 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
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all] What versions of java do we support?

[Rob Tompkins]

> On Mar 21, 2019, at 10:22 PM, Bernd Eckenfels  wrote:
> 
> Nearly all vendors I have seen announced to follow voluntarily or commercial 
> guaranteed the OpenJDK LTS versions (11, some 8) (Redhat, adoptopenjdk, Azul, 
> ojdkbuild, sapengine, Amazon, Ubuntu/Debian, suse). Actually only Oracle‘s 
> OpenJDK is not.
> 

Cool. Then pardon my being tied to a vendor. 

Regardless, I suppose the question remains the same though right? We should be 
compatible with both 8 and 11.

-Rob

> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> ________
> Von: Rob Tompkins 
> Gesendet: Freitag, März 22, 2019 2:59 AM
> An: Commons Developers List
> Betreff: Re: [all] What versions of java do we support?
> 
> Is there LTS with those other imolementations?
> 
>> On Mar 21, 2019, at 9:43 PM, Ralph Goers  wrote:
>> 
>> Why are you singling out Corretto? What about AdoptOpenJDK or RedHat’s 
>> OpenJDK support? The ASF is supposed to be vendor neutral.
>> 
>> Ralph
>> 
>>> On Mar 21, 2019, at 11:05 AM, Rob Tompkins  wrote:
>>> 
>>> Hello all,
>>> 
>>> I would think that with the Amazon Corretto play at long term support for 
>>> java 8 and 11 we would want to build using the latest version of the 
>>> Corretto 8-JDK, and we would want to ensure that we work for Java 11. 
>>> Regarding later versions of Java I’m a tad agnostic currently as we are 
>>> less certain with their stability.
>>> 
>>> What are folks’ thoughts?
>>> 
>>> -Rob
>>> -
>>> 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
>> 
> 
> -
> 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

Re: [LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

> On Mar 22, 2019, at 8:40 AM, Gary Gregory  wrote:
> 
> +1
> 
> Testing RC tag checkout.
> 
> Not a blocker, the changes.xml file needs a release date and description.

Doh. Thanks.

> 
> Using:
> 
> mvn clean package site
> 
> On:
> 
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
> 2018-10-24T14:41:47-04:00)
> Maven home: C:\Java\apache-maven-3.6.0\bin\..
> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_202\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.16299.904]
> 
> RAT check OK.
> 
> Gary
> 
> 
> On Wed, Mar 20, 2019 at 11:29 AM Rob Tompkins  wrote:
> 
>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Parent 47 was released, so I would like to release
>> Apache Commons Parent 48.
>> 
>> Apache Commons Parent 48 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1
>> (svn revision 33098)
>> 
>> 
>> The Git tag commons-parent-48-RC1 commit for this RC is
>> f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162
>> 
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>> --branch commons-parent-48-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/
>> 
>> These are the Maven artifacts:
>> 
>> #Release SHA-512s
>> #Wed Mar 20 11:07:15 EDT 2019
>> 
>> commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
>> 
>> commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
>> 
>> commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
>> 
>> commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
>> 
>> commons-parent-48-src-tar.gz=b52eb5416ad28356ac24b54fb6ee831919584606f71f99cd7cfc7bd00e92fd40ae1e838bb9d7a6f2914d777313b0c7682fbbe6a158845be3461f75d9c120cfd4
>> 
>> 
>> 
>> 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 47 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site
>>(note some *relative* links are broken and the 48 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-parent/48-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.
>>

Re: [codec] Java 8

[Rob Tompkins]

+1, but there are considerable projects out there that would want us to 
maintain backwards compatibility with Java 7. 

> On Mar 22, 2019, at 11:12 AM, Gary Gregory  wrote:
> 
> Hi All,
> 
> Now that Codec 1.12 is out, I plan on updating from Java 7 to Java 8.
> 
> Gary

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [codec] Java 8

[Rob Tompkins]

That seems reasonable. 

> On Mar 22, 2019, at 11:23 AM, Gary Gregory  wrote:
> 
> This comes up from time to time and I can only offer my usual "if you want
> support for a dead version of Java, feel free to provide a PR" We can
> always provide 1.12.1 for Java 7 security fixes or other fixes deemed
> important enough.
> 
> Gary
> 
>> On Fri, Mar 22, 2019 at 11:20 AM Rob Tompkins  wrote:
>> 
>> +1, but there are considerable projects out there that would want us to
>> maintain backwards compatibility with Java 7.
>> 
>>> On Mar 22, 2019, at 11:12 AM, Gary Gregory 
>> wrote:
>>> 
>>> Hi All,
>>> 
>>> Now that Codec 1.12 is out, I plan on updating from Java 7 to Java 8.
>>> 
>>> Gary
>> 
>> -
>> 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

Re: [LANG] Jenkins Pipeline DSL

[Rob Tompkins]

Killer. Nice work.

> On Mar 23, 2019, at 8:58 AM, Benedikt Ritter  wrote:
> 
> Hi!
> 
> the PR has been merged and I've created a multi branch pipeline [1]. I've
> used the configuration from the PLC4X project because I know they were
> among the first to use pipeline files. I recommend that we let this build
> for a while to get a feeling whether this works the way we want. If it does
> we can then drop the old manually configured pipeline.
> 
> Regards,
> Benedikt
> 
> [1]
> https://builds.apache.org/view/A-D/view/Commons/job/commons-lang-pipeline/

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

Good question. I am.  But I won’t be able to finish things up until tomorrow. 
It’s been a hectic week...couple of night shifts friend in from out of town and 
such. 

-Rob

> On Mar 24, 2019, at 11:16 AM, Gary Gregory  wrote:
> 
> All done? ;-)
> 
> Gary
> 
>> On Fri, Mar 22, 2019 at 8:55 AM Rob Tompkins  wrote:
>> 
>> 
>> 
>>> On Mar 22, 2019, at 8:40 AM, Gary Gregory 
>> wrote:
>>> 
>>> +1
>>> 
>>> Testing RC tag checkout.
>>> 
>>> Not a blocker, the changes.xml file needs a release date and description.
>> 
>> Doh. Thanks.
>> 
>>> 
>>> Using:
>>> 
>>> mvn clean package site
>>> 
>>> On:
>>> 
>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>> 2018-10-24T14:41:47-04:00)
>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: C:\Program
>>> Files\Java\jdk1.8.0_202\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> Microsoft Windows [Version 10.0.16299.904]
>>> 
>>> RAT check OK.
>>> 
>>> Gary
>>> 
>>> 
>>> On Wed, Mar 20, 2019 at 11:29 AM Rob Tompkins 
>> wrote:
>>> 
>>>> We have fixed quite a few bugs and added some significant enhancements
>>>> since Apache Commons Parent 47 was released, so I would like to release
>>>> Apache Commons Parent 48.
>>>> 
>>>> Apache Commons Parent 48 RC1 is available for review here:
>>>>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1
>>>> (svn revision 33098)
>>>> 
>>>> 
>>>> The Git tag commons-parent-48-RC1 commit for this RC is
>>>> f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:
>>>> 
>>>> 
>> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162
>>>> 
>>>> You may checkout this tag using:
>>>>   git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>>>> --branch commons-parent-48-RC1
>>>> 
>>>> Maven artifacts are here:
>>>> 
>>>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/
>>>> 
>>>> These are the Maven artifacts:
>>>> 
>>>> #Release SHA-512s
>>>> #Wed Mar 20 11:07:15 EDT 2019
>>>> 
>>>> 
>> commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
>>>> 
>>>> 
>> commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
>>>> 
>>>> 
>> commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
>>>> 
>>>> 
>> commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
>>>> 
>>>> 
>> commons-parent-48-src-tar.gz=b52eb5416ad28356ac24b54fb6ee831919584606f71f99cd7cfc7bd00e92fd40ae1e838bb9d7a6f2914d777313b0c7682fbbe6a158845be3461f75d9c120cfd4
>>>> 
>>>> 
>>>> 
>>>> 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 47 are in the release notes:
>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/RELEASE-NOTES.txt
>>>> 
>>>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site/changes-re

Re: [LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

Ah. Then I’ll promote it right now and button the rest up tomorrow. 

> On Mar 24, 2019, at 11:50 AM, Gary Gregory  wrote:
> 
> If you can just do the release from Nexus bit, then I can use the new
> parent. I might RC [vfs].
> 
> Gary
> 
>> On Sun, Mar 24, 2019 at 11:32 AM Rob Tompkins  wrote:
>> 
>> Good question. I am.  But I won’t be able to finish things up until
>> tomorrow. It’s been a hectic week...couple of night shifts friend in from
>> out of town and such.
>> 
>> -Rob
>> 
>>> On Mar 24, 2019, at 11:16 AM, Gary Gregory 
>> wrote:
>>> 
>>> All done? ;-)
>>> 
>>> Gary
>>> 
>>>> On Fri, Mar 22, 2019 at 8:55 AM Rob Tompkins 
>> wrote:
>>>> 
>>>> 
>>>> 
>>>>> On Mar 22, 2019, at 8:40 AM, Gary Gregory 
>>>> wrote:
>>>>> 
>>>>> +1
>>>>> 
>>>>> Testing RC tag checkout.
>>>>> 
>>>>> Not a blocker, the changes.xml file needs a release date and
>> description.
>>>> 
>>>> Doh. Thanks.
>>>> 
>>>>> 
>>>>> Using:
>>>>> 
>>>>> mvn clean package site
>>>>> 
>>>>> On:
>>>>> 
>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>> 2018-10-24T14:41:47-04:00)
>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
>> C:\Program
>>>>> Files\Java\jdk1.8.0_202\jre
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>> "windows"
>>>>> Microsoft Windows [Version 10.0.16299.904]
>>>>> 
>>>>> RAT check OK.
>>>>> 
>>>>> Gary
>>>>> 
>>>>> 
>>>>> On Wed, Mar 20, 2019 at 11:29 AM Rob Tompkins 
>>>> wrote:
>>>>> 
>>>>>> We have fixed quite a few bugs and added some significant enhancements
>>>>>> since Apache Commons Parent 47 was released, so I would like to
>> release
>>>>>> Apache Commons Parent 48.
>>>>>> 
>>>>>> Apache Commons Parent 48 RC1 is available for review here:
>>>>>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1
>>>>>> (svn revision 33098)
>>>>>> 
>>>>>> 
>>>>>> The Git tag commons-parent-48-RC1 commit for this RC is
>>>>>> f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:
>>>>>> 
>>>>>> 
>>>> 
>> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162
>>>>>> 
>>>>>> You may checkout this tag using:
>>>>>>  git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>>>>>> --branch commons-parent-48-RC1
>>>>>> 
>>>>>> Maven artifacts are here:
>>>>>> 
>>>>>> 
>>>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/
>>>>>> 
>>>>>> These are the Maven artifacts:
>>>>>> 
>>>>>> #Release SHA-512s
>>>>>> #Wed Mar 20 11:07:15 EDT 2019
>>>>>> 
>>>>>> 
>>>> 
>> commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
>>>>>> 
>>>>>> 
>>>> 
>> commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
>>>>>> 
>>>>>> 
>>>> 
>> commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
>>>>>> 
>>>>>> 
>>>> 
>> commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
>>>>>> 
>>>>>> 
>>>> 
>&g

Re: [LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

Here’s my +1.

-Rob

> On Mar 20, 2019, at 11:22 AM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Parent 47 was released, so I would like to release Apache 
> Commons Parent 48.
> 
> Apache Commons Parent 48 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1 (svn 
> revision 33098)
> 
> 
> The Git tag commons-parent-48-RC1 commit for this RC is 
> f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162
> 
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-parent.git --branch 
> commons-parent-48-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/
> 
> These are the Maven artifacts:
> 
> #Release SHA-512s
> #Wed Mar 20 11:07:15 EDT 2019
> commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
> commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
> commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
> commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
> commons-parent-48-src-tar.gz=b52eb5416ad28356ac24b54fb6ee831919584606f71f99cd7cfc7bd00e92fd40ae1e838bb9d7a6f2914d777313b0c7682fbbe6a158845be3461f75d9c120cfd4
> 
> 
> 
> 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 47 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site
>(note some *relative* links are broken and the 48 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-parent/48-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:
> 
> git clone https://gitbox.apache.org/repos/asf/commons-parent.git -b 
> commons-parent-48-RC1
> cd commons-parent-48-RC1
> 
> 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

[RESULT][LAZY][VOTE] Release Apache Commons Parent 48 based on RC1

[Rob Tompkins]

With the votes of:

Gary Gregory: +1, and
my: +1

this vote passes. I will perform the release mechanics over the next day and a 
half.

-ROb :-)

> On Mar 20, 2019, at 11:22 AM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Parent 47 was released, so I would like to release Apache 
> Commons Parent 48.
> 
> Apache Commons Parent 48 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1 (svn 
> revision 33098)
> 
> 
> The Git tag commons-parent-48-RC1 commit for this RC is 
> f613ac722733b5e10a7028a635b7717d30fbb162 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f613ac722733b5e10a7028a635b7717d30fbb162
> 
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-parent.git --branch 
> commons-parent-48-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-${commons.nexus.repo.id}/org/apache/commons/commons-parent/48/
> 
> These are the Maven artifacts:
> 
> #Release SHA-512s
> #Wed Mar 20 11:07:15 EDT 2019
> commons-parent-48-src-zip=037e8e118e3d52f41b5a6682bef83dc716770e39dd7cc677762ff777c4e42f67eb5a1722684a35b68ed205cd82a5b1e9eb49927d759490d50817deef1a566caf
> commons-parent-48-javadoc-javadoc=541be566d3e7a80a8ee6c90bb2973d346ad125932ac3f42e8b901f76a6a2ac5a918cc4bc1725b9c17ad5ab8c60b7e348f33f0a4f154659aef7c64636e04eaca5
> commons-parent-48-site-xml=8dcd3a5fbef28277caa8a9f201d786e61d39fb7a00f4a5dfe3103a3a6fc403648327af83295ff2ab5d51c27b966156a499554860535770aaaeb4271ea20a2e69
> commons-parent-48-pom=6873a43261b38dcb241a30f4e947f425f10c3de2cfbdf6b684e813ff0d7feddd56fcc6f96a357e430fb98cbf05cba64fd9b516f79d5bc47311f2e60a6e334ed6
> commons-parent-48-src-tar.gz=b52eb5416ad28356ac24b54fb6ee831919584606f71f99cd7cfc7bd00e92fd40ae1e838bb9d7a6f2914d777313b0c7682fbbe6a158845be3461f75d9c120cfd4
> 
> 
> 
> 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 47 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/48-RC1/site
>(note some *relative* links are broken and the 48 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-parent/48-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:
> 
> git clone https://gitbox.apache.org/repos/asf/commons-parent.git -b 
> commons-parent-48-RC1
> cd commons-parent-48-RC1
> 
> 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

Re: [codec] RAT check in Jenkins vs local

[Rob Tompkins]

That’s likely a consequence of this commit: 
https://github.com/apache/commons-parent/commit/30a0eaea5a3efb14f2e81bcae4aaf06ff9a91bd8
 
,
 but I dont’ have a good answer for you on the jenkins build yet. I’ve got to 
catch back up from yesterday’s roadshow event on my emails before I can get 
answers there.

-Rob

> On Mar 26, 2019, at 10:05 AM, Gary Gregory  wrote:
> 
> Hi All:
> 
> When I run a RAT check with 'mvn apache-rat:check', all is fine. When I run
> the same kind of build as Jenkins with 'mvn clean package', all is fine.
> 
> Why does the Jenkins build fail its RAT check?
> 
> https://builds.apache.org/job/Commons-Codec/104/console
> 
> Gary

[ANNOUNCE] Commons Parent 48 released.

[Rob Tompkins]

[This announcement is only going to the dev list.] 

Hello All,

Commons Parent 48 has been released.

Changes in this version include:

Fixed Bugs:
o Revert revert change in commons.scmPubUrl in Parent 47, use commons.packageId 
for osgi
o Revert change in commons.scmPubUrl in Parent 47  Issue: COMMONSSITE-124.
o re-enabled japicmp and introduced japicmp.skip property that
controls whether japicmp reports are run. It is disabled by
default and enabled via a special profile enabled by the
presence of the file src/site/resources/profile.japicmp
- org.apache.felix:maven-bundle-plugin 3.5.0 -> 3.5.1

Changes:
o Run "apache-rat:check" as part of "mvn validate"
o commons.build-plugin.version: 1.9 -> 1.10
o commons.release-plugin.version: 1.5 -> 1.6
o commons.spotbugs.version: 3.1.3 -> 3.1.6
o japicmp-maven-plugin: 0.12.0 -> 0.13.0
o Update parent from org.apache:apache 19 to 20.
o maven-compiler-plugin 3.7.0 -> 3.8.0
o org.apache.felix:maven-bundle-plugin 3.5.0 -> 3.5.1
o org.jacoco:jacoco-maven-plugin 0.8.1 -> 0.8.3 (Java 11)
o org.apache.maven.wagon:wagon-ssh 3.1.0 -> 3.2.0
o maven-surefire-plugin 2.22.0 -> 2.22.1
o maven-surefire-report-plugin 2.22.0 -> 2.22.1
o maven-failsafe-plugin 2.22.0 -> 2.22.1
o versions-maven-plugin 2.5 -> 2.7
o org.apache.felix:maven-bundle-plugin 3.5.1 -> 4.1.0
o maven-jxr-plugin 2.5 -> 3.0.0
o org.apache.rat:apache-rat-plugin 0.12 -> 0.13
o commons.wagon-ssh.version 3.2.0 -> 3.3.1
o maven-assembly-plugin 3.1.0 -> 3.1.1
o commons.jar-plugin.version 3.1.0 -> 3.1.1
o commons.animal-sniffer.version 1.16 -> 1.17
o org.apache.bcel:bcel 6.2 -> 6.3
o commons-release-plugin 1.4 -> 1.5
o org.apache.maven.wagon:wagon-ssh 3.3.1 -> 3.3.2
o org.apache.maven.plugins:maven-javadoc-plugin 3.0.1 -> 3.1.0

Cheers,
-Rob

Re: [GSoC] Submission of Final Draft for GSoC Proposal

[Rob Tompkins]

> On Apr 1, 2019, at 7:03 PM, Gilles Sadowski  wrote:
> 
>> Le lun. 1 avr. 2019 à 23:54, Abhishek Dhadwal  a 
>> écrit :
>> 
>> Dear Alex sir and Giles sir,
>> May I submit the final draft for the proposal, or should I make any changes
>> before submission ?
>> The drive Link for the proposal: :
>> https://docs.google.com/document/d/1dKwGTDYWrqae26v3DdLljvZw9reEfaO5h2vyO1rWRG8/edit?usp=sharing
> 
> Looks OK to me.
> 
> Gilles
> 
> P.S. Whenever you have time, don't hesitate to start contributing.
> 

+1 to that :-)

>> 
>> Regards,
>> Abhishek
> 
> -
> 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

[lang] Towards 3.9

[Rob Tompkins]

Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us to go 
up with what we have. Any thoughts for or against doing a release?

-Rob

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [lang] Towards 3.9

[Rob Tompkins]

> On Apr 4, 2019, at 9:20 AM, Gilles Sadowski  wrote:
> 
>> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us to 
>> go up with what we have. Any thoughts for or against doing a release?
> 
> Any objection to fixing
>https://issues.apache.org/jira/projects/LANG/issues/LANG-1442 
> 

Yes. I think that we should definitely put commons-rng in the 
RandomUtils/RandomStringUtils javadoc.

-Rob

> ?
> 
> Gilles
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

Re: [all] Should we use MathJaX in Javadoc on all repos? (Was: Re: [jira] [Commented] (NUMBERS-58) Javadoc: Use MathJaX)

[Rob Tompkins]

> On Apr 5, 2019, at 5:12 AM, Alex Herbert  wrote:
> 
>> On 05/04/2019 09:27, sebb wrote:
>>> On Tue, 12 Mar 2019 at 12:28, Rob Tompkins  wrote:
>>> For those unfamiliar with MathJaX, is the javascript mechanism for 
>>> accommodating for LaTeX (the math typesetting language, written by Donald 
>>> Knuth) in html.
>>> 
>>> It could be convenient to use mathematical notation in our javadoc 
>>> generally. That said, Java doesn’t do this so it would indeed be 
>>> non-standard. My opinion is in the +0.5 zone currently.
>>> 
>>> Thoughts?
>>> 
>> Is it likely that existing Javadoc comments will trigger MathJaX?
>> That would perhaps mean lots of changes just to stay still.
>> 
>> What does it look like if JavaScript is not in use?
> 
> Not very readable. Have a look at this page:
> 
> http://commons.apache.org/proper/commons-math/javadocs/api-3.6.1/org/apache/commons/math3/analysis/polynomials/PolynomialsUtils.html
> 
> Then turn off Javascript (e.g. [1]) and look again.
> 
> An example non-javascript output for an equation (method 
> createJacobiPolynomial(int, int, int)) is:
> 
> \( P_0^{vw}(x) = 1 \\ P_{-1}^{vw}(x) = 0 \\ 2k(k + v + w)(2k + v + w - 2) 
> P_k^{vw}(x) = \\ (2k + v + w - 1)[(2k + v + w)(2k + v + w - 2) x + v^2 - w^2] 
> P_{k-1}^{vw}(x) \\ - 2(k + v - 1)(k + w - 1)(2k + v + w) P_{k-2}^{vw}(x) \)
> 

I suppose that depends on one’s familiarity with LaTeX :-p

Definitely a fair point because the above is indeed ugly

> 
> [1] https://www.lifewire.com/disable-javascript-in-google-chrome-4103631
> 
>> 
>> I think it would be sensible for the processing to be optional, e.g.
>> via a marker file.
>> 
>> -
>> 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
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all] Should we use MathJaX in Javadoc on all repos? (Was: Re: [jira] [Commented] (NUMBERS-58) Javadoc: Use MathJaX)

[Rob Tompkins]

There should be an unsubscribe link on this page:

https://commons.apache.org/mail-lists.html

> On Apr 5, 2019, at 9:13 AM, Javin Paul  wrote:
> 
> How to unsubscribe from this group?
> 
> On Fri, Apr 5, 2019 at 8:24 PM Alex Herbert 
> wrote:
> 
>> On 05/04/2019 12:06, Gilles Sadowski wrote:
>>>>>> On 05/04/2019 09:27, sebb wrote:
>>>>>> On Tue, 12 Mar 2019 at 12:28, Rob Tompkins  wrote:
>>>>>> For those unfamiliar with MathJaX, is the javascript mechanism for
>> accommodating for LaTeX (the math typesetting language, written by Donald
>> Knuth) in html.
>>>>>> 
>>>>>> It could be convenient to use mathematical notation in our javadoc
>> generally. That said, Java doesn’t do this so it would indeed be
>> non-standard. My opinion is in the +0.5 zone currently.
>>>>>> 
>>>>>> Thoughts?
>>>>> Is it likely that existing Javadoc comments will trigger MathJaX?
>>>>> That would perhaps mean lots of changes just to stay still.
>>>>> 
>>>>> What does it look like if JavaScript is not in use?
>>>> Not very readable. Have a look at this page:
>>> If one knows LaTeX somewhat, it's fairly readable.
>>> Another advantage is that, within the source code, it is
>>> more readable than the equivalent formula in HTML.
>>> E.g. compare
>>>   r1x1
>>> with
>>>   \( r_1 x_1 \)
>> 
>> So this depends on the use case:
>> 
>> Use case
>>LaTex
>>HTML
>> Reading the Javadoc online  Nice equations. Needs Javascript enabled.
>> 
>> Q. Is disabling Javascript common?
>>OK equations. No need for Javascript.
>> Accessing the Javadoc in an IDE No equations. Needs fluency in
>> LaTeX.
>> Can resort to viewing Javadocs in a browser (with Javscript).   OK
>> equations.
>> Reading the source code No equations. Needs fluency in LaTeX. Can
>> resort to viewing Javadocs in a browser (with Javscript).   Verbose
>> HTML
>> equations. Needs fluency in HTML. Can view Javadocs in an IDE/browser.
>> Maintaining the source code LaTex is easier to write complex equations.
>> 
>> IDE cannot show the Javadoc.
>> 
>> Javadoc tool cannot spot errors.
>> 
>> Javadoc must be built and viewed locally before commit.
>>Verbose HTML equations. Some equations not easily possible without
>> imagination.
>> 
>> IDE can show the Javadoc for a quick check.
>> 
>> Javadoc tool can spot errors so can be part of a series of checks for a PR.
>> 
>> 
>> In the common use case I question if the disabling of Javascript in a
>> browser is a common thing nowadays? Using LaTeX will be better. Someone
>> who sees the pages without Javascript and raises a bug will be kindly
>> directed towards enabling Javascript in their browser for the
>> commons.apache.org host.
>> 
>> In the developer use case then an IDE can support the HTML which is
>> nice. It can be used for simple equations. For the LaTeX I think that a
>> developer is quite capable of understanding what is going on and can
>> open a browser to view the Javadoc if needed.
>> 
>> For reading the source code it is the same as above. If you got this far
>> then you can figure it out.
>> 
>> In the source code maintainer use case then writing the HTML for a
>> complex equation is more work than using LaTeX. But the equations cannot
>> be checked by Javadoc. So the onus is on the developer who wants to use
>> LaTeX to render the javadocs and make sure they look correct.
>> 
>> 
>> So to allow MathJax in any commons project would require an explicit
>> validation of the LaTeX that may be present in any PR or new commit.
>> 
>> My vote is to enable via a profile (as Sebb suggested) and let the
>> project developers decide if they want to maintain it.
>> 
>> 
>> http://commons.apache.org/proper/commons-math/javadocs/api-3.6.1/org/apache/commons/math3/analysis/polynomials/PolynomialsUtils.html
>>>> 
>>>> Then turn off Javascript (e.g. [1]) and look again.
>>>> 
>>>> An example non-javascript output for an equation (method
>>>> createJacobiPolynomial(int, int, int)) is:
>>>> 
>>>> \( P_0^{vw}(x) = 1 \\ P_{-1}^{vw}(x) = 0 \\ 2k(k + v + w)(2k + v + w -
>>>> 2) P_k^{vw}(x) = \\ (2k + v + w - 1)[(2k + v + w)(2k + v + w - 2) x +
>>>> v^2 - w^2] P_{k-1}^{vw}(x) \\ - 2(k + v - 1)(k + w - 1)(2k 

Re: [lang] Towards 3.9

[Rob Tompkins]

> On Apr 6, 2019, at 9:42 AM, Gilles Sadowski  wrote:
> 
> Hi Rob.
> 
> Le ven. 5 avr. 2019 à 04:27, Rob Tompkins  a écrit :
>> 
>> 
>> 
>>> On Apr 4, 2019, at 9:20 AM, Gilles Sadowski  wrote:
>>> 
>>>> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us 
>>>> to go up with what we have. Any thoughts for or against doing a release?
>>> 
>>> Any objection to fixing
>>>   https://issues.apache.org/jira/projects/LANG/issues/LANG-1442 
>>> <https://issues.apache.org/jira/projects/LANG/issues/LANG-1442>
>> 
>> Yes. I think that we should definitely put commons-rng in the 
>> RandomUtils/RandomStringUtils javadoc.
> 
> Thanks for commit 3f43706192b1b75c5023f165534a12b192c31442

Your point made sense to me. -Rob

> 
> Gilles
> 
> 
>> -Rob
>> 
>>> ?
>>> 
>>> Gilles
>>> 
>>> -
>>> 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
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [lang] Towards 3.9

[Rob Tompkins]

> On Apr 6, 2019, at 9:52 AM, Rob Tompkins  wrote:
> 
> 
> 
>> On Apr 6, 2019, at 9:42 AM, Gilles Sadowski  wrote:
>> 
>> Hi Rob.
>> 
>> Le ven. 5 avr. 2019 à 04:27, Rob Tompkins  a écrit :
>>> 
>>> 
>>> 
>>>> On Apr 4, 2019, at 9:20 AM, Gilles Sadowski  wrote:
>>>> 
>>>>> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us 
>>>>> to go up with what we have. Any thoughts for or against doing a release?
>>>> 
>>>> Any objection to fixing
>>>>  https://issues.apache.org/jira/projects/LANG/issues/LANG-1442 
>>>> <https://issues.apache.org/jira/projects/LANG/issues/LANG-1442>
>>> 
>>> Yes. I think that we should definitely put commons-rng in the 
>>> RandomUtils/RandomStringUtils javadoc.
>> 
>> Thanks for commit 3f43706192b1b75c5023f165534a12b192c31442
> 
> Your point made sense to me. -Rob

And no worries :-)

> 
>> 
>> Gilles
>> 
>> 
>>> -Rob
>>> 
>>>> ?
>>>> 
>>>> Gilles
>>>> 
>>>> -
>>>> 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

Re: [lang] Towards 3.9

[Rob Tompkins]

> On Apr 6, 2019, at 10:00 AM, Jochen Wiedmann  
> wrote:
> 
> On Fri, Apr 5, 2019 at 4:27 AM Rob Tompkins  wrote:
>> 
>>> On Apr 4, 2019, at 9:20 AM, Gilles Sadowski  wrote:
>>> 
>>>> Any thoughts on doing a 3.9 release of [lang]. I think Benedikt want’s us 
>>>> to go up with what we have. Any thoughts for or against doing a release?
>>> 
>>> Any objection to fixing
>>>   https://issues.apache.org/jira/projects/LANG/issues/LANG-1442 
>>> <https://issues.apache.org/jira/projects/LANG/issues/LANG-1442>
>> 
>> Yes. I think that we should definitely put commons-rng in the 
>> RandomUtils/RandomStringUtils javadoc.
> 
> Disagreed, because commons-lang should not have any dependencies.
> SecureRandom should be completely sufficient, should it?

Oh pardon….I was vague. I meant that to mean that we should refer in the 
javadoc to Commons-RNG.

-Rob

> 
> Jochen
> 
> -
> 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

[lang] LANG-1442

[Rob Tompkins]

@Gilles - thoughts on this wording: 
https://github.com/apache/commons-lang/commit/3f43706192b1b75c5023f165534a12b192c31442
 

 ?

-Rob

[release-plugin] sha’s (Was: Re: [VOTE] Release Apache Commons Pool 2.6.2 based on RC1)

[Rob Tompkins]

> On Apr 6, 2019, at 12:24 PM, Gary Gregory  wrote:
> 
> Hi Sebb,
> 
> Thank you for your review. Some comments below.
> 
>> On Sat, Apr 6, 2019 at 5:00 AM sebb  wrote:
>> 
>>> On Sat, 6 Apr 2019 at 03:15, Gary Gregory  wrote:
>>> 
>>> We have fixed a few bugs since Apache Commons Pool 2.6.1 was released,
>> so I
>>> would like to release Apache Commons Pool 2.6.2.
>>> 
>>> Apache Commons Pool 2.6.2 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1 (svn
>>> revision 33480)
>>> 
>>> The Git tag commons-pool-2.6.2-RC1 commit for this RC is
>>> 06de412e2ce72007a6e43112164c371de4a66d3b which you can browse here:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=06de412e2ce72007a6e43112164c371de4a66d3b
>>> You may checkout this tag using:
>>>git clone https://gitbox.apache.org/repos/asf/commons-pool.git -b
>>> commons-pool-2.6.2-RC1 commons-pool-2.6.2-RC1
>>> 
>>> Maven artifacts are here:
>>> 
>>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1432/org/apache/commons/commons-pool2/2.6.2/
>>> 
>>> These are the Maven artifacts and their hashes in Nexus:
>>> 
>>> #Release SHA-512s
>>> #Fri Apr 05 21:23:42 EDT 2019
>>> 
>> commons-pool2-2.6.2-test-sources-java-source=7494677ccb265bca20fa61fd143f8a5f2e518653926c9a8ca5b33a6b379f9c9c5c262613839ff722200c7053356cbf6fb3a436823c4d6bf504dce4782a206373
>> 
>> What is commons-pool2-2.6.2-test-sources-java-source ?
>> 
> 
> Looks like a SNAFU in our release plugin; sorted, the entries should be:

That’s on me :-)

I used dashes in there for consistency in property naming, but in hindsight 
it’s more confusing. I’m planning on switching it to the file name verbatim.

Do we want to include the sha1’s of the nexus “convenience” artifacts? We can 
do this, but have hesitated to in the past.

-Rob

> 
> commons-pool2-2.6.2-bin-tar.gz
> SHA512
> 8bf3b5bdd81c88761421e45ae8904e9718f152d09124880cf0acdcf08e7e64ab9a16eed23977f871bc8365801e3a7d4b1af254dd83fcdadca43520f7399b140e
> 
> commons-pool2-2.6.2-bin.zip
> SHA512
> f80ef3718b319f4c2d0605466a49947598d74f1c50d0c3e53d7603f022f3d78d56b3b1291cf0f6382d20642dd4782d87b55c6f56b49475281e21179dbfae4fcd
> 
> commons-pool2-2.6.2-src-tar.gz
> SHA512
> a02f34c5e38bbcf2f1960cc1b89f468e6c4229b7d5f48b60044dd7a670d2a00eaab08fa8eca7b135b2696fe7a09824fcafe7ab3c4513716d1a4003f0bb3c0336
> 
> commons-pool2-2.6.2-src.zip
> SHA512
> 86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
> 
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-javadoc.jar
> (SHA1: 16cea19174aa457aa254572b9a439926adc4f02a)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-test-sources.jar
> (SHA1: df34b03e3af2183cce59faa892b2fbd6adacfea1)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-test-sources.jar.asc
> (SHA1: 11e34225a509129a726781fb8f179d1c08f4f43f)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.jar.asc
> (SHA1: a80bf487ec6a5a5a40b8e0437ea3e27557a8002d)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-tests.jar
> (SHA1: 5b9c9a358fe3d168e53640c324efe1e98acc5c2d)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.pom.asc
> (SHA1: 2e6509d0e77e52dd4cd466a4adf0b046525995ce)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.jar
> (SHA1: 775a8072995b29eafe8fb0a828a190589f71cede)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-javadoc.jar.asc
> (SHA1: 82702906bd6c04e56f79fe78570ef090dd2c7680)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-sources.jar
> (SHA1: 730e1f4e0af8513090412fbbfb8075e625770fc0)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-tests.jar.asc
> (SHA1: 4fe9ab98ebc9ccc8362319260145b2450f6e94ef)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.pom
> (SHA1: 597c26594bbf7c24f41603c507fbfdae92cb567e)
> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-sources.jar.asc
> (SHA1: b691db5b596325e2cb2fca6c71a6d1b8b4bb71c6)
> 
> 
>>> 
>> commons-pool2-2.6.2-src-zip=86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
>>> 
>> commons-pool2-2.6.2-sources-java-source=7984cabeda669cb84d54dc65cfe8992ee73bc87b9cb32853482649fe3bb09062f48ee3fe739ec141dad17c071853d6a8ef2ad4a738ceb532b71d49722fa914d0
>> 
>> Ditto commons-pool2-2.6.2-sources-java-source ?
>> 
>>> 
>> commons-pool2-2.6.2-pom.asc=0c2aa02dbac198db0b13d928130c258f1cf9f1e6432a2aedb3639401fb15b332245378cf439b735da61b024d2032ca889133586062cd01c548adcae5c57c82fa
>>> 
>> commons-pool2-2.6.2-tests-jar.asc=c4eab9e7200a9ef6577af29889982d60febf0534e7cddb57950049044ffaece22aacd1ced22aed0fc8c8a5236e5423afdfe445c0da517b9f5d6c33a4cc71e321
>>> 
>> commons-pool2-2.6.2-bin-zip.asc=66c004f5805eecf897bdf007d746489e1eaf74d484d6136b72bcac0a5654f45be351b83fe6015880c1581a8b143f913b29aff07462c28371e5e6483bf28e1687
>>> 
>> commons-po

Re: [release-plugin] sha’s (Was: Re: [VOTE] Release Apache Commons Pool 2.6.2 based on RC1)

[Rob Tompkins]

> On Apr 7, 2019, at 5:52 AM, sebb  wrote:
> 
>> On Sat, 6 Apr 2019 at 17:59, Gary Gregory  wrote:
>> 
>>> On Sat, Apr 6, 2019 at 12:48 PM Rob Tompkins  wrote:
>>> 
>>> 
>>> 
>>>> On Apr 6, 2019, at 12:24 PM, Gary Gregory  wrote:
>>>> 
>>>> Hi Sebb,
>>>> 
>>>> Thank you for your review. Some comments below.
>>>> 
>>>>>> On Sat, Apr 6, 2019 at 5:00 AM sebb  wrote:
>>>>>> 
>>>>>> On Sat, 6 Apr 2019 at 03:15, Gary Gregory  wrote:
>>>>>> 
>>>>>> We have fixed a few bugs since Apache Commons Pool 2.6.1 was released,
>>>>> so I
>>>>>> would like to release Apache Commons Pool 2.6.2.
>>>>>> 
>>>>>> Apache Commons Pool 2.6.2 RC1 is available for review here:
>>>>>>   https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1 (svn
>>>>>> revision 33480)
>>>>>> 
>>>>>> The Git tag commons-pool-2.6.2-RC1 commit for this RC is
>>>>>> 06de412e2ce72007a6e43112164c371de4a66d3b which you can browse here:
>>>>>> 
>>>>>> 
>>>>> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=06de412e2ce72007a6e43112164c371de4a66d3b
>>>>>> You may checkout this tag using:
>>>>>>   git clone https://gitbox.apache.org/repos/asf/commons-pool.git -b
>>>>>> commons-pool-2.6.2-RC1 commons-pool-2.6.2-RC1
>>>>>> 
>>>>>> Maven artifacts are here:
>>>>>> 
>>>>>> 
>>>>> https://repository.apache.org/content/repositories/orgapachecommons-1432/org/apache/commons/commons-pool2/2.6.2/
>>>>>> 
>>>>>> These are the Maven artifacts and their hashes in Nexus:
>>>>>> 
>>>>>> #Release SHA-512s
>>>>>> #Fri Apr 05 21:23:42 EDT 2019
>>>>>> 
>>>>> commons-pool2-2.6.2-test-sources-java-source=7494677ccb265bca20fa61fd143f8a5f2e518653926c9a8ca5b33a6b379f9c9c5c262613839ff722200c7053356cbf6fb3a436823c4d6bf504dce4782a206373
>>>>> 
>>>>> What is commons-pool2-2.6.2-test-sources-java-source ?
>>>>> 
>>>> 
>>>> Looks like a SNAFU in our release plugin; sorted, the entries should be:
>>> 
>>> That’s on me :-)
>>> 
>>> I used dashes in there for consistency in property naming, but in hindsight 
>>> it’s more confusing. I’m planning on switching it to the file name verbatim.
>>> 
>>> Do we want to include the sha1’s of the nexus “convenience” artifacts? We 
>>> can do this, but have hesitated to in the past.
>> 
>> 
>> On our page http://commons.apache.org/releases/prepare.html I read: "Also 
>> the revisions for the various tags, and hashes for the release artifacts", 
>> which I interpret as having the vote email contain the hashes of any files 
>> we release on Nexus and Dist folders.
>> 
>> @Sebastian Bazley  WDYT?
> 
> The intention of the hash is to tie the published artifacts back to the VOTE.
> 
> So I thjnk we need hashes of all the artifacts that are listed in the VOTE.
> This includes the convenience artifacts as they should be checked too.
> e.g. they can be checked for valid N&L files and spurious content
> 

Cool. Do we want the hashes to be those that nexus stores, namely the sha1’s, 
or do we think they need to be the more secure sha512?

-Rob


>> Gary
>> 
>>> 
>>> -Rob
>>> 
>>>> 
>>>> commons-pool2-2.6.2-bin-tar.gz
>>>> SHA512
>>>> 8bf3b5bdd81c88761421e45ae8904e9718f152d09124880cf0acdcf08e7e64ab9a16eed23977f871bc8365801e3a7d4b1af254dd83fcdadca43520f7399b140e
>>>> 
>>>> commons-pool2-2.6.2-bin.zip
>>>> SHA512
>>>> f80ef3718b319f4c2d0605466a49947598d74f1c50d0c3e53d7603f022f3d78d56b3b1291cf0f6382d20642dd4782d87b55c6f56b49475281e21179dbfae4fcd
>>>> 
>>>> commons-pool2-2.6.2-src-tar.gz
>>>> SHA512
>>>> a02f34c5e38bbcf2f1960cc1b89f468e6c4229b7d5f48b60044dd7a670d2a00eaab08fa8eca7b135b2696fe7a09824fcafe7ab3c4513716d1a4003f0bb3c0336
>>>> 
>>>> commons-pool2-2.6.2-src.zip
>>>> SHA512
>>>> 86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
>>>> 
>>>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-javadoc.j

Re: [commons-release-plugin] branch master updated: Use final.

[Rob Tompkins]

Thanks...pardon my being overly busy yesterday. Taxes and a take home exercise 
under a deadline kept me too busy. I’ll try to get to this and the release of 
[lang] 3.9 over the next few days. 

-Rob

> On Apr 7, 2019, at 9:37 AM, ggreg...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> ggregory pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git
> 
> 
> The following commit(s) were added to refs/heads/master by this push:
> new 9dfa6b3  Use final.
> 9dfa6b3 is described below
> 
> commit 9dfa6b3a872d58590f18f8f925f4f8e3afedb7b1
> Author: Gary Gregory 
> AuthorDate: Sun Apr 7 09:37:51 2019 -0400
> 
>Use final.
> ---
> .../commons/release/plugin/SharedFunctions.java| 18 ++---
> .../mojos/CommonsDistributionDetachmentMojo.java   | 38 +-
> .../mojos/CommonsDistributionStagingMojo.java  | 80 +++---
> .../plugin/mojos/CommonsSiteCompressionMojo.java   | 18 ++---
> .../plugin/mojos/CommonsStagingCleanupMojo.java| 20 +++---
> .../velocity/HeaderHtmlVelocityDelegate.java   |  8 +--
> .../velocity/ReadmeHtmlVelocityDelegate.java   | 22 +++---
> .../CommonsDistributionDetachmentMojoTest.java | 36 +-
> .../mojos/CommonsDistributionStagingMojoTest.java | 60 
> .../mojos/CommonsSiteCompressionMojoTest.java  | 16 ++---
> .../mojos/CommonsStagingCleanupMojoTest.java   |  8 +--
> .../stubs/DistributionDetachmentProjectStub.java   |  4 +-
> .../velocity/HeaderHtmlVelocityDelegateTest.java   |  2 +-
> .../velocity/ReadmeHtmlVelocityDelegateTest.java   | 12 ++--
> 14 files changed, 171 insertions(+), 171 deletions(-)
> 
> diff --git 
> a/src/main/java/org/apache/commons/release/plugin/SharedFunctions.java 
> b/src/main/java/org/apache/commons/release/plugin/SharedFunctions.java
> index feb786d..fb04950 100755
> --- a/src/main/java/org/apache/commons/release/plugin/SharedFunctions.java
> +++ b/src/main/java/org/apache/commons/release/plugin/SharedFunctions.java
> @@ -60,7 +60,7 @@ public final class SharedFunctions {
>  * @throws MojoExecutionException when an {@link IOException} or {@link 
> NullPointerException} is caught for the
>  *  purpose of bubbling the exception up to Maven properly.
>  */
> -public static void initDirectory(Log log, File workingDirectory) throws 
> MojoExecutionException {
> +public static void initDirectory(final Log log, final File 
> workingDirectory) throws MojoExecutionException {
> if (workingDirectory.exists()) {
> try {
> FileUtils.deleteDirectory(workingDirectory);
> @@ -85,7 +85,7 @@ public final class SharedFunctions {
>  * @param toFile the {@link File} to which to copy into.
>  * @throws MojoExecutionException if an {@link IOException} or {@link 
> NullPointerException} is caught.
>  */
> -public static void copyFile(Log log, File fromFile, File toFile) throws 
> MojoExecutionException {
> +public static void copyFile(final Log log, final File fromFile, final 
> File toFile) throws MojoExecutionException {
> try {
> FileUtils.copyFile(fromFile, toFile);
> } catch (IOException | NullPointerException e) {
> @@ -104,13 +104,13 @@ public final class SharedFunctions {
>  * @param username temp.
>  * @param password temp.
>  */
> -public static void setAuthentication(ScmProviderRepository 
> providerRepository,
> -   String distServer,
> -   Settings settings,
> -   SettingsDecrypter settingsDecrypter,
> -   String username,
> -   String password) {
> -Optional server =
> +public static void setAuthentication(final ScmProviderRepository 
> providerRepository,
> +   final String distServer,
> +   final Settings settings,
> +   final SettingsDecrypter settingsDecrypter,
> +   final String username,
> +   final String password) {
> +final Optional server =
> 
> Optional.ofNullable(distServer).map(settings::getServer).map(DefaultSettingsDecryptionRequest::new)
> 
> .map(settingsDecrypter::decrypt).map(SettingsDecryptionResult::getServer);
> 
> diff --git 
> a/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
>  
> b/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> index 285cb0a..9c54c1e 100755
> --- 
> a/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> +++ 
> b/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> @@ -62,7 +62,7 @@ publ

Re: [commons-lang] branch master updated: (docs) update user use -> user explore

[Rob Tompkins]

I think that maybe hits what you guys were getting after with my wording. 

And you know me, english as a first language, still writing poorly :-p

Do we think lang 3.9 is ready?

-Rob 

> On Apr 8, 2019, at 8:13 AM, chtom...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> chtompki pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/commons-lang.git
> 
> 
> The following commit(s) were added to refs/heads/master by this push:
> new 69326c8  (docs) update user use -> user explore
> 69326c8 is described below
> 
> commit 69326c8ba9d4b0399701ab3de40ed20d35f9e248
> Author: Tompkins 
> AuthorDate: Mon Apr 8 08:13:39 2019 -0400
> 
>(docs) update user use -> user explore
> ---
> src/main/java/org/apache/commons/lang3/RandomStringUtils.java | 2 +-
> src/main/java/org/apache/commons/lang3/RandomUtils.java   | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/src/main/java/org/apache/commons/lang3/RandomStringUtils.java 
> b/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
> index 9fe6684..e0472c9 100644
> --- a/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
> +++ b/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
> @@ -40,7 +40,7 @@ import java.util.Random;
>  * We would like to further note to users that the Apache Commons Project 
> has
>  * a component entirely dedicated to random number generation, namely
>  * http://commons.apache.org/rng";>Commons RNG. For a more 
> extensive
> - * treatment of random numbers, we suggest that the user use this 
> library.
> + * treatment of random numbers, we suggest that the user explore this 
> library.
>  *
>  * #ThreadSafe#
>  * @since 1.0
> diff --git a/src/main/java/org/apache/commons/lang3/RandomUtils.java 
> b/src/main/java/org/apache/commons/lang3/RandomUtils.java
> index 6f1b3b9..4d37b9e 100644
> --- a/src/main/java/org/apache/commons/lang3/RandomUtils.java
> +++ b/src/main/java/org/apache/commons/lang3/RandomUtils.java
> @@ -28,7 +28,7 @@ import java.util.Random;
>  * We would like to further note to users that the Apache Commons Project 
> has
>  * a component entirely dedicated to random number generation, namely
>  * http://commons.apache.org/rng";>Commons RNG. For a more 
> extensive
> - * treatment of random numbers, we suggest that the user use this 
> library.
> + * treatment of random numbers, we suggest that the user explore this 
> library.
>  *
>  * @since 3.3
>  */
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-lang] branch master updated: (docs) update user use -> user explore

[Rob Tompkins]

> On Apr 8, 2019, at 9:35 AM, sebb  wrote:
> 
> On Mon, 8 Apr 2019 at 14:25, Gilles Sadowski  <mailto:gillese...@gmail.com>> wrote:
>> 
>> Hi Rob.
>> 
>> Le lun. 8 avr. 2019 à 14:16, Rob Tompkins > <mailto:chtom...@apache.org>> a écrit :
>>> 
>>> I think that maybe hits what you guys were getting after with my wording.
>> 
>> You probably missed a thread.
>> I've just committed the alternative text.
> 
> Looks good to me.

+1

> 
>> Regards,
>> Gilles
>> 
>>> 
>>> And you know me, english as a first language, still writing poorly :-p
>>> 
>>> Do we think lang 3.9 is ready?
>>> 
>>> -Rob
>>> 
>>>> On Apr 8, 2019, at 8:13 AM, chtom...@apache.org wrote:
>>>> 
>>>> This is an automated email from the ASF dual-hosted git repository.
>>>> 
>>>> chtompki pushed a commit to branch master
>>>> in repository https://gitbox.apache.org/repos/asf/commons-lang.git
>>>> 
>>>> 
>>>> The following commit(s) were added to refs/heads/master by this push:
>>>>new 69326c8  (docs) update user use -> user explore
>>>> 69326c8 is described below
>>>> 
>>>> commit 69326c8ba9d4b0399701ab3de40ed20d35f9e248
>>>> Author: Tompkins 
>>>> AuthorDate: Mon Apr 8 08:13:39 2019 -0400
>>>> 
>>>>   (docs) update user use -> user explore
>>>> ---
>>>> src/main/java/org/apache/commons/lang3/RandomStringUtils.java | 2 +-
>>>> src/main/java/org/apache/commons/lang3/RandomUtils.java   | 2 +-
>>>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>>> 
>>>> diff --git a/src/main/java/org/apache/commons/lang3/RandomStringUtils.java 
>>>> b/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
>>>> index 9fe6684..e0472c9 100644
>>>> --- a/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
>>>> +++ b/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
>>>> @@ -40,7 +40,7 @@ import java.util.Random;
>>>> * We would like to further note to users that the Apache Commons 
>>>> Project has
>>>> * a component entirely dedicated to random number generation, namely
>>>> * http://commons.apache.org/rng";>Commons RNG. For a more 
>>>> extensive
>>>> - * treatment of random numbers, we suggest that the user use this 
>>>> library.
>>>> + * treatment of random numbers, we suggest that the user explore this 
>>>> library.
>>>> *
>>>> * #ThreadSafe#
>>>> * @since 1.0
>>>> diff --git a/src/main/java/org/apache/commons/lang3/RandomUtils.java 
>>>> b/src/main/java/org/apache/commons/lang3/RandomUtils.java
>>>> index 6f1b3b9..4d37b9e 100644
>>>> --- a/src/main/java/org/apache/commons/lang3/RandomUtils.java
>>>> +++ b/src/main/java/org/apache/commons/lang3/RandomUtils.java
>>>> @@ -28,7 +28,7 @@ import java.util.Random;
>>>> * We would like to further note to users that the Apache Commons 
>>>> Project has
>>>> * a component entirely dedicated to random number generation, namely
>>>> * http://commons.apache.org/rng";>Commons RNG. For a more 
>>>> extensive
>>>> - * treatment of random numbers, we suggest that the user use this 
>>>> library.
>>>> + * treatment of random numbers, we suggest that the user explore this 
>>>> library.
>>>> *
>>>> * @since 3.3
>>>> */
>>>> 
>>> 
>>> 
>>> -
>>> 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
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> <mailto:dev-unsubscr...@commons.apache.org>
> For additional commands, e-mail: dev-h...@commons.apache.org 
> <mailto:dev-h...@commons.apache.org>

Re: [VOTE] Release Apache Commons Pool 2.6.2 based on RC1

[Rob Tompkins]

Looking.

> On Apr 8, 2019, at 10:15 AM, Gary Gregory  wrote:
> 
> Looking for VOTEs...
> 
> Gary
> 
> On Sat, Apr 6, 2019 at 12:24 PM Gary Gregory  wrote:
> 
>> Hi Sebb,
>> 
>> Thank you for your review. Some comments below.
>> 
>> On Sat, Apr 6, 2019 at 5:00 AM sebb  wrote:
>> 
>>> On Sat, 6 Apr 2019 at 03:15, Gary Gregory  wrote:
 
 We have fixed a few bugs since Apache Commons Pool 2.6.1 was released,
>>> so I
 would like to release Apache Commons Pool 2.6.2.
 
 Apache Commons Pool 2.6.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1 (svn
 revision 33480)
 
 The Git tag commons-pool-2.6.2-RC1 commit for this RC is
 06de412e2ce72007a6e43112164c371de4a66d3b which you can browse here:
 
 
>>> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=06de412e2ce72007a6e43112164c371de4a66d3b
 You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-pool.git -b
 commons-pool-2.6.2-RC1 commons-pool-2.6.2-RC1
 
 Maven artifacts are here:
 
 
>>> https://repository.apache.org/content/repositories/orgapachecommons-1432/org/apache/commons/commons-pool2/2.6.2/
 
 These are the Maven artifacts and their hashes in Nexus:
 
 #Release SHA-512s
 #Fri Apr 05 21:23:42 EDT 2019
 
>>> commons-pool2-2.6.2-test-sources-java-source=7494677ccb265bca20fa61fd143f8a5f2e518653926c9a8ca5b33a6b379f9c9c5c262613839ff722200c7053356cbf6fb3a436823c4d6bf504dce4782a206373
>>> 
>>> What is commons-pool2-2.6.2-test-sources-java-source ?
>>> 
>> 
>> Looks like a SNAFU in our release plugin; sorted, the entries should be:
>> 
>> commons-pool2-2.6.2-bin-tar.gz
>> SHA512
>> 8bf3b5bdd81c88761421e45ae8904e9718f152d09124880cf0acdcf08e7e64ab9a16eed23977f871bc8365801e3a7d4b1af254dd83fcdadca43520f7399b140e
>> 
>> commons-pool2-2.6.2-bin.zip
>> SHA512
>> f80ef3718b319f4c2d0605466a49947598d74f1c50d0c3e53d7603f022f3d78d56b3b1291cf0f6382d20642dd4782d87b55c6f56b49475281e21179dbfae4fcd
>> 
>> commons-pool2-2.6.2-src-tar.gz
>> SHA512
>> a02f34c5e38bbcf2f1960cc1b89f468e6c4229b7d5f48b60044dd7a670d2a00eaab08fa8eca7b135b2696fe7a09824fcafe7ab3c4513716d1a4003f0bb3c0336
>> 
>> commons-pool2-2.6.2-src.zip
>> SHA512
>> 86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
>> 
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-javadoc.jar
>> (SHA1: 16cea19174aa457aa254572b9a439926adc4f02a)
>> 
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-test-sources.jar
>> (SHA1: df34b03e3af2183cce59faa892b2fbd6adacfea1)
>> 
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-test-sources.jar.asc
>> (SHA1: 11e34225a509129a726781fb8f179d1c08f4f43f)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.jar.asc
>> (SHA1: a80bf487ec6a5a5a40b8e0437ea3e27557a8002d)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-tests.jar
>> (SHA1: 5b9c9a358fe3d168e53640c324efe1e98acc5c2d)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.pom.asc
>> (SHA1: 2e6509d0e77e52dd4cd466a4adf0b046525995ce)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.jar
>> (SHA1: 775a8072995b29eafe8fb0a828a190589f71cede)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-javadoc.jar.asc
>> (SHA1: 82702906bd6c04e56f79fe78570ef090dd2c7680)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-sources.jar
>> (SHA1: 730e1f4e0af8513090412fbbfb8075e625770fc0)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-tests.jar.asc
>> (SHA1: 4fe9ab98ebc9ccc8362319260145b2450f6e94ef)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2.pom
>> (SHA1: 597c26594bbf7c24f41603c507fbfdae92cb567e)
>> /org/apache/commons/commons-pool2/2.6.2/commons-pool2-2.6.2-sources.jar.asc
>> (SHA1: b691db5b596325e2cb2fca6c71a6d1b8b4bb71c6)
>> 
>> 
 
>>> commons-pool2-2.6.2-src-zip=86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
 
>>> commons-pool2-2.6.2-sources-java-source=7984cabeda669cb84d54dc65cfe8992ee73bc87b9cb32853482649fe3bb09062f48ee3fe739ec141dad17c071853d6a8ef2ad4a738ceb532b71d49722fa914d0
>>> 
>>> Ditto commons-pool2-2.6.2-sources-java-source ?
>>> 
 
>>> commons-pool2-2.6.2-pom.asc=0c2aa02dbac198db0b13d928130c258f1cf9f1e6432a2aedb3639401fb15b332245378cf439b735da61b024d2032ca889133586062cd01c548adcae5c57c82fa
 
>>> commons-pool2-2.6.2-tests-jar.asc=c4eab9e7200a9ef6577af29889982d60febf0534e7cddb57950049044ffaece22aacd1ced22aed0fc8c8a5236e5423afdfe445c0da517b9f5d6c33a4cc71e321
 
>>> commons-pool2-2.6.2-bin-zip.asc=66c004f5805eecf897bdf007d746489e1eaf74d484d6136b72bcac0a5654f45be351b83fe6015880c1581a8b143f913b29aff07462c28371e5e6483bf28e1687
 
>>> commons-pool2-2.6.2-src-tar.gz=a02f34c5e38bbcf2f1960cc1b89f468e6c4229b7d5f48b60044dd7a670d2a00eaab08fa8eca7b1

Re: [VOTE] Release Apache Commons Pool 2.6.2 based on RC1

[Rob Tompkins]

+1

Build with java 8 and java 11 ok ‘mvn clean package site’

all reports look ok (some static analysis nits).

jacoco doesn’t exist in the reports on the site (nit)

signatures all check out.

-Rob

> On Apr 5, 2019, at 10:15 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs since Apache Commons Pool 2.6.1 was released, so I
> would like to release Apache Commons Pool 2.6.2.
> 
> Apache Commons Pool 2.6.2 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1 (svn
> revision 33480)
> 
> The Git tag commons-pool-2.6.2-RC1 commit for this RC is
> 06de412e2ce72007a6e43112164c371de4a66d3b which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=06de412e2ce72007a6e43112164c371de4a66d3b
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-pool.git -b
> commons-pool-2.6.2-RC1 commons-pool-2.6.2-RC1
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1432/org/apache/commons/commons-pool2/2.6.2/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Release SHA-512s
> #Fri Apr 05 21:23:42 EDT 2019
> commons-pool2-2.6.2-test-sources-java-source=7494677ccb265bca20fa61fd143f8a5f2e518653926c9a8ca5b33a6b379f9c9c5c262613839ff722200c7053356cbf6fb3a436823c4d6bf504dce4782a206373
> commons-pool2-2.6.2-src-zip=86a8e77b6d50ab57c2e9374a6f1d1e3d66946e541f90eacc822126026901ba4f172ddb0549f101c62757cb0389e23751063bb0e97128699aa9d8a7b8c5ebbd7a
> commons-pool2-2.6.2-sources-java-source=7984cabeda669cb84d54dc65cfe8992ee73bc87b9cb32853482649fe3bb09062f48ee3fe739ec141dad17c071853d6a8ef2ad4a738ceb532b71d49722fa914d0
> commons-pool2-2.6.2-pom.asc=0c2aa02dbac198db0b13d928130c258f1cf9f1e6432a2aedb3639401fb15b332245378cf439b735da61b024d2032ca889133586062cd01c548adcae5c57c82fa
> commons-pool2-2.6.2-tests-jar.asc=c4eab9e7200a9ef6577af29889982d60febf0534e7cddb57950049044ffaece22aacd1ced22aed0fc8c8a5236e5423afdfe445c0da517b9f5d6c33a4cc71e321
> commons-pool2-2.6.2-bin-zip.asc=66c004f5805eecf897bdf007d746489e1eaf74d484d6136b72bcac0a5654f45be351b83fe6015880c1581a8b143f913b29aff07462c28371e5e6483bf28e1687
> commons-pool2-2.6.2-src-tar.gz=a02f34c5e38bbcf2f1960cc1b89f468e6c4229b7d5f48b60044dd7a670d2a00eaab08fa8eca7b135b2696fe7a09824fcafe7ab3c4513716d1a4003f0bb3c0336
> commons-pool2-2.6.2-javadoc-jar.asc=97ab6e2ecf47ec356f8514d51325652468469e99d819769014dbbd1fe77830d27c4efbb4389116052369af5ccc18167a98a1dedda0243a2cf98942e98c05ba45
> commons-pool2-2.6.2-test-sources-jar.asc=141122c4aebb25f72d91f208d9b6912c0ecc1b1dedc41972ee281bc6b54c6222ff4993d5c8ad6ab939e5154109f226f67206bb34bed913c6ee00a76c9ba21260
> commons-pool2-2.6.2-bin-tar.gz.asc=67a787a210e787a1f74d0fa4af9c3708ed236c70aa4329e202d6bec0837b23a7779a72a358d02b7ee99d2a6d2eaaf8b01c0d7b2e404e742e9e8aca54bd0377fe
> commons-pool2-2.6.2-sources-jar.asc=ec62de6a0c294687abffe56a5faea5725e704b792593e7ea3a12b7837cccf476f69c70fe7d8f19ef67a7f1a6bb5f28cbbc239e37cd396caf530bcca7acf6057a
> commons-pool2-2.6.2-bin-tar.gz=8bf3b5bdd81c88761421e45ae8904e9718f152d09124880cf0acdcf08e7e64ab9a16eed23977f871bc8365801e3a7d4b1af254dd83fcdadca43520f7399b140e
> commons-pool2-2.6.2-javadoc-javadoc=31504dce4d3e7ef638dcdec1bcbef15467837cf80c21c3fc9a89abcaf2e04de6b2a33165ea3ac809ba3fa27410d7dc6dbe7bb1773b73f9045c73a8081a1f9e17
> commons-pool2-2.6.2-src-tar.gz.asc=61ae67fb0c9aa6e6760dfbe73c554642acace81a5f1cfa84cd5cdeab1ceb8fe122899514db185ef91920881a5ca9124e93c423f632bc02dd186705719a502eeb
> commons-pool2-2.6.2-src-zip.asc=523227eca9aac3fbb2dc118e1a7cc62f79541bc29362c4d3c0923e4f19f4dcb1e2562422e849f90243d840b32ff9ce9787df0491753c7f6b3d0667d95d53e666
> commons-pool2-2.6.2-tests-test-jar=c8f9df3a4b8c9eb291a173846cacbdf7d29aa0ba34936889ae825873d82cdfb25ed5e66f728260d1b64bee4d19e7256e3b0052eb099909a0baaa65027960ce81
> commons-pool2-2.6.2-jar.asc=fe3b932a97ca44c4c2c7a41b015b184d9e8d21ba2197f1157ba71f60808b735ada20b6c1cfacc4f6fbc59ea5c0f0cbbe957c6ab2c16892f18b6f911497e795d8
> commons-pool2-2.6.2-bin-zip=f80ef3718b319f4c2d0605466a49947598d74f1c50d0c3e53d7603f022f3d78d56b3b1291cf0f6382d20642dd4782d87b55c6f56b49475281e21179dbfae4fcd
> 
> (no need for .asc hashes!)
> 
> I have tested this with 'clean package site' using:
> 
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
> 2018-10-24T14:41:47-04:00)
> Maven home: C:\Java\apache-maven-3.6.0\bin\..
> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_202\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.16299.967]
> 
> Details of changes since 2.6.1 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/pool/2.6.2-RC1/

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

[Rob Tompkins]

> On Apr 9, 2019, at 7:21 AM, Gilles Sadowski  wrote:
> 
> Le mar. 9 avr. 2019 à 13:03, sebb  > a écrit :
>> 
>> On Tue, 9 Apr 2019 at 11:43, Gilles Sadowski  wrote:
>>> 
 [...]
> 
> $ git diff pom.xml
> diff --git a/pom.xml b/pom.xml
> index 2612dd6..54a88e4 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -570,6 +570,7 @@
>   
> ${implementation.build}
>   
> ${maven.compiler.source}
>   
> ${maven.compiler.target}
> +  
> ${commons.module.name}
>>> 
>>> ${commons.automatic.module.name}
>>> 
> 
>   
> 
> @@ -1608,6 +1609,9 @@
> 1.3
> 1.3
> 
> +
> +${project.artifactId}
>>> 
>>> No default should be defined (to avoid the risk of creating incompatible
>>> but identically named modules).
>> 
>> Surely that *should* be solved by using groupId + artifactId?
> 
> From
>https://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html 
> 
> ---CUT---
> Module names must be valid Java identifiers! E.g. no Java keywords, no
> dashes, no...
> ---CUT---
> 
>> We change one or the other when releasing an incompatible module.
>> 
>>> Then the release plugin could be enhanced (?) so that it would check
>>> whether the variable has been defined for each JAR to be created (and
>>> fail the build otherwise).
>> 
>> But how would that ensure incompatible modules were given different names?
> 
> It would not.
> [IIUC, same issue with OSGI config.]

If it’s the same issue as OSGI, should we not then use the same value as we do 
with OSGI, which we already have?

> 
>> 
>>> Gilles
>>> 
> +
> 
> false
> 
> 
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org

[lang] 3.9, switch from cobertura to jacoco?

[Rob Tompkins]

Thoughts on doing this switch? I’m heavily leaning towards it because I can’t 
get code coverage to work on java 11 with the current build.

-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [lang] 3.9, switch from cobertura to jacoco?

[Rob Tompkins]

We want a jira for this?

-Rob

> On Apr 9, 2019, at 9:14 AM, Gary Gregory  wrote:
> 
> +1
> 
> Gary
> 
> On Tue, Apr 9, 2019 at 8:39 AM Rob Tompkins  wrote:
> 
>> Thoughts on doing this switch? I’m heavily leaning towards it because I
>> can’t get code coverage to work on java 11 with the current build.
>> 
>> -Rob
>> -
>> 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

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

[Rob Tompkins]

> On Apr 9, 2019, at 11:57 AM, sebb  wrote:
> 
> On Tue, 9 Apr 2019 at 16:53, Jochen Wiedmann  
> wrote:
>> 
>> On Tue, Apr 9, 2019 at 3:51 PM sebb  wrote:
>> 
>>> We already have a process for ensuring that Maven coords and package
>>> names are changed when API breaks.
>>> Do we really want to have yet another name that has to be maintained?
>> 
>> What's the alternative?
> 
> As I already wrote, use the gid + aid to generate a suitable name.

We already do this for OSGI here’s the [lang] example: 
https://github.com/apache/commons-lang/blob/master/pom.xml#L581 
 combined with 
https://github.com/apache/commons-parent/blob/master/pom.xml#L1743 




> 
>> 
>>> Being able to define the module name independently is all very well,
>>> but it does not solve the problem of ensuring that the module name is
>>> correct, and remains correct when code is updated.
>> 
>> That is, IMO, a problem, which can (and will) be solved later.
> 
> Which may involve reverting the work already done.
> 
>> Jochen
>> 
>> -
>> 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
> 

Re: ***UNCHECKED*** [parent] Introducing Automatic-Module-Name

[Rob Tompkins]

> On Apr 9, 2019, at 1:11 PM, sebb  wrote:
> 
> On Tue, 9 Apr 2019 at 17:06, Rob Tompkins  <mailto:chtom...@gmail.com>> wrote:
>> 
>> 
>> 
>>> On Apr 9, 2019, at 11:57 AM, sebb  wrote:
>>> 
>>> On Tue, 9 Apr 2019 at 16:53, Jochen Wiedmann  
>>> wrote:
>>>> 
>>>> On Tue, Apr 9, 2019 at 3:51 PM sebb  wrote:
>>>> 
>>>>> We already have a process for ensuring that Maven coords and package
>>>>> names are changed when API breaks.
>>>>> Do we really want to have yet another name that has to be maintained?
>>>> 
>>>> What's the alternative?
>>> 
>>> As I already wrote, use the gid + aid to generate a suitable name.
>> 
>> We already do this for OSGI here’s the [lang] example: 
>> https://github.com/apache/commons-lang/blob/master/pom.xml#L581 
>> <https://github.com/apache/commons-lang/blob/master/pom.xml#L581> 
>> <https://github.com/apache/commons-lang/blob/master/pom.xml#L581 
>> <https://github.com/apache/commons-lang/blob/master/pom.xml#L581>> combined 
>> with https://github.com/apache/commons-parent/blob/master/pom.xml#L1743 
>> <https://github.com/apache/commons-parent/blob/master/pom.xml#L1743> 
>> <https://github.com/apache/commons-parent/blob/master/pom.xml#L1743 
>> <https://github.com/apache/commons-parent/blob/master/pom.xml#L1743>>
> 
> I think 'org.apache.commons' should probably be: ${project.groupId} in CP.
> Otherwise projects that are still on a different groupId may get a
> duplicate conflicting name if they move to o.a.c as the groupId.

I’m a +1 to that idea, but it is worth noting that we do have antiquated 
groupId’s that look like “commons-” in the project. They would have 
to be changed at their next release.

-Rob

> 
>> 
>> 
>> 
>>> 
>>>> 
>>>>> Being able to define the module name independently is all very well,
>>>>> but it does not solve the problem of ensuring that the module name is
>>>>> correct, and remains correct when code is updated.
>>>> 
>>>> That is, IMO, a problem, which can (and will) be solved later.
>>> 
>>> Which may involve reverting the work already done.
>>> 
>>>> Jochen
>>>> 
>>>> -
>>>> 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
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> <mailto:dev-unsubscr...@commons.apache.org>
> For additional commands, e-mail: dev-h...@commons.apache.org 
> <mailto:dev-h...@commons.apache.org>

[VOTE] Release Apache Commons Lang 3.9 based on RC1

[Rob Tompkins]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons Lang 3.8.1 was released, so I would like to release Apache 
Commons Lang 3.9.

Apache Commons Lang 3.9 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1 (svn revision 
33538)

The Git tag commons-lang-3.9-RC1 commit for this RC is 
8b378885152075b44c5710d6dbcb8df4a5fb3223 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=8b378885152075b44c5710d6dbcb8df4a5fb3223
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch 
commons-lang-3.9-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1433/org/apache/commons/commons-lang3/3.9/

These are the Maven artifacts and their hashes in Nexus:

#Nexus SHA-1s
commons-lang3-3.9-sources.jar=6dce2c1ea3cbb6c438b2313786a501b38e5ad7b0
commons-lang3-3.9.pom=a0204d47009f50de96af0b87acfd1c6b3b16419a
commons-lang3-3.9-javadoc.jar=c643c72d73f70ed7d71783f3ce8f37b057e33777
commons-lang3-3.9.jar=d76bbd8a0213744a14af3ba80ab3ab69b02bdbae
commons-lang3-3.9-tests.jar=411ede8701d31196bc28c2c60607e6de47da4922
commons-lang3-3.9-test-sources.jar=a28a97bb8d4fa3e05230d3eed5b8f934f3f55889


#Release SHA-512s
#Tue Apr 09 14:23:45 EDT 2019
commons-lang3-3.9-src.tar.gz=8e85013ae7629b205ed39c54f9c14d8d7801c47226373ccb0482a0149dbf9c7654d6b5c81815b594f45b4426917bbe1618db7ba6758665e39771efbb98c49e20
commons-lang3-3.9-bin.tar.gz=8ebaa30565d80d32dbb1ba19047f61027fd043294b85aa1f6f1613c7ac4739da030ff2a5ea2ad119283d13fb5db7b41c1bd784f95828cb9727a3f7e9f302d9fc
commons-lang3-3.9-src.zip=30595b6f5df73aca6542bb70c626234d6ec43e2f11316f7a5123982ba100027437b7ecc44bbfd0f665152c3e98e997bc145d7976b33a48526aa6d929a8c1f7ad
commons-lang3-3.9-bin.zip=072c67c4793e7f4fa070202ab5ebe3fa29d81bfd23982a00bfd1d752e54991b696042ba791706458f9993d3721198f08fce70a6f9d1f16fd94d6cc54856393f8


I have tested this with 'mvn clean test package 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_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.4", arch: "x86_64", family: "mac"


Details of changes since 3.8.1 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site
(note some *relative* links are broken and the 3.9 directories are not yet 
created - these will be OK once the site is deployed.)

CLIRR Report (compared to 3.8.1):

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/clirr-report.html

JApiCmp Report (compared to 3.8.1):

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-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:

git clone https://gitbox.apache.org/repos/asf/lang.git -b commons-lang-3.9-RC1
cd commons-lang-3.9-RC1

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

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

[Rob Tompkins]

gram
> Files\Java\openjdk\jdk-13\bin\java"
> -javaagent:C:\\Users\\ggregory\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\temp\\rc\\commons-lang\\target\\jacoco.exec
> -Xmx512m --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens
> java.base/java.lang=ALL-UNNAMED -jar
> C:\Users\ggregory\AppData\Local\Temp\surefire5519858828807362694\surefirebooter988663828837655366.jar
> C:\Users\ggregory\AppData\Local\Temp\surefire5519858828807362694
> 2019-04-09T21-13-37_709-jvmRun1 surefire11717302241379819897tmp
> surefire_07095889889312770815tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
> [ERROR] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [ERROR] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]     at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at
> java.base/java.lang.reflect.Method.invoke(Method.java:567)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR]
> [ERROR] -> [Help 1]
> 
> Gary
> 
> On Tue, Apr 9, 2019 at 3:37 PM Rob Tompkins  wrote:
> 
>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Lang 3.8.1 was released, so I would like to release
>> Apache Commons Lang 3.9.
>> 
>> Apache Commons Lang 3.9 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1 (svn
>> revision 33538)
>> 
>> The Git tag commons-lang-3.9-RC1 commit for this RC is
>> 8b378885152075b44c5710d6dbcb8df4a5fb3223 which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=8b378885152075b44c5710d6dbcb8df4a5fb3223
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-lang.git
>> --branch commons-lang-3.9-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/c

[lang] Remove final modifier behaviour in java 12+ (was: Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1)

[Rob Tompkins]

Looks like we get an exception because the final modifier isn’t removable in 
java 12+ and for good reason [1]. So, we probably should throw an exception, 
but both of the exceptions that arise out of the jvm here 
https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736
 
<https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736>
 are checked exceptions. Specifically we get a “NoSuchFieldException” when we 
attempt to retrieve “modifiers” from the “Field.” For the sake of retaining BC, 
I would think that we would in turn convert that Exception to an 
“UnsupportedOperationException”  or a “TypeNotPresentException” (maybe ??) for 
the sake of getting to an unchecked exception.

Open to thoughts here,

-Rob


[1] 
http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-November/056486.html


> On Apr 10, 2019, at 5:09 AM, Benedikt Ritter  wrote:
> 
> Damn it, I had it on my list to fix those. Sorry, Rob!
> 
> Am Mi., 10. Apr. 2019 um 03:33 Uhr schrieb Rob Tompkins > :
> 
>> 
>> 
>>> On Apr 9, 2019, at 9:15 PM, Gary Gregory  wrote:
>>> 
>>> +0... see Java 12 testing below.
>> 
>> That +0 is almost worth cancelling for in my opinion. I’ll wait until
>> tomorrow to see if anyone else wants to have an opinion here, and then I’ll
>> have another go at it.
>> 
>> -Rob
>> 
>>> 
>>> Nit in the release notes: Replace "Java 8.0" with Java 8".
>>> 
>>> From the git tag, ran 'mvn -V clean package' OK for:
>>> 
>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>> 2018-10-24T14:41:47-04:00)
>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: C:\Program
>>> Files\Java\jdk1.8.0_202\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> 
>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>> 2018-10-24T14:41:47-04:00)
>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>> Java version: 11.0.2, vendor: Oracle Corporation, runtime: C:\Program
>>> Files\Java\openjdk\jdk-11.0.2
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> 
>>> BUT on Java 12:
>>> 
>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>> 2018-10-24T14:41:47-04:00)
>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>> Java version: 12, vendor: Oracle Corporation, runtime: C:\Program
>>> Files\Java\openjdk\jdk-12
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> 
>>> I get:
>>> 
>>> [ERROR] Failures:
>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifier:998 expected: 
>> but
>>> was: 
>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifierWithAccess:1009 expected:
>>>  but was: 
>>> [INFO]
>>> [ERROR] Tests run: 5774, Failures: 2, Errors: 0, Skipped: 4
>>> 
>>> On Java 13-EA:
>>> 
>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>> 2018-10-24T14:41:47-04:00)
>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>> Java version: 13-ea, vendor: Oracle Corporation, runtime: C:\Program
>>> Files\Java\openjdk\jdk-13
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> 
>>> I get:
>>> 
>>> [INFO] ---
>>> [INFO]  T E S T S
>>> [INFO] ---
>>> [WARNING] Corrupted STDOUT by directly writing to native stream in forked
>>> JVM 1. See FAQ web page and the dump file
>>> 
>> C:\temp\rc\commons-lang\target\surefire-reports\2019-04-09T21-13-37_709-jvmRun1.dumpstream
>>> [INFO]
>>> [INFO] Results:
>>> [INFO]
>>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>> [INFO]
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>

[CANCEL][VOTE] Release Apache Commons Lang 3.9 based on RC1

[Rob Tompkins]

I’m going to cancel this [VOTE] so that we can button up those java 12 problems 
and upversion jacoco and surefire.

-Rob

> On Apr 9, 2019, at 3:37 PM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Lang 3.8.1 was released, so I would like to release Apache 
> Commons Lang 3.9.
> 
> Apache Commons Lang 3.9 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1 (svn revision 
> 33538)
> 
> The Git tag commons-lang-3.9-RC1 commit for this RC is 
> 8b378885152075b44c5710d6dbcb8df4a5fb3223 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=8b378885152075b44c5710d6dbcb8df4a5fb3223
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch 
> commons-lang-3.9-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1433/org/apache/commons/commons-lang3/3.9/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus SHA-1s
> commons-lang3-3.9-sources.jar=6dce2c1ea3cbb6c438b2313786a501b38e5ad7b0
> commons-lang3-3.9.pom=a0204d47009f50de96af0b87acfd1c6b3b16419a
> commons-lang3-3.9-javadoc.jar=c643c72d73f70ed7d71783f3ce8f37b057e33777
> commons-lang3-3.9.jar=d76bbd8a0213744a14af3ba80ab3ab69b02bdbae
> commons-lang3-3.9-tests.jar=411ede8701d31196bc28c2c60607e6de47da4922
> commons-lang3-3.9-test-sources.jar=a28a97bb8d4fa3e05230d3eed5b8f934f3f55889
> 
> 
> #Release SHA-512s
> #Tue Apr 09 14:23:45 EDT 2019
> commons-lang3-3.9-src.tar.gz=8e85013ae7629b205ed39c54f9c14d8d7801c47226373ccb0482a0149dbf9c7654d6b5c81815b594f45b4426917bbe1618db7ba6758665e39771efbb98c49e20
> commons-lang3-3.9-bin.tar.gz=8ebaa30565d80d32dbb1ba19047f61027fd043294b85aa1f6f1613c7ac4739da030ff2a5ea2ad119283d13fb5db7b41c1bd784f95828cb9727a3f7e9f302d9fc
> commons-lang3-3.9-src.zip=30595b6f5df73aca6542bb70c626234d6ec43e2f11316f7a5123982ba100027437b7ecc44bbfd0f665152c3e98e997bc145d7976b33a48526aa6d929a8c1f7ad
> commons-lang3-3.9-bin.zip=072c67c4793e7f4fa070202ab5ebe3fa29d81bfd23982a00bfd1d752e54991b696042ba791706458f9993d3721198f08fce70a6f9d1f16fd94d6cc54856393f8
> 
> 
> I have tested this with 'mvn clean test package 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_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.4", arch: "x86_64", family: "mac"
> 
> 
> Details of changes since 3.8.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site
>(note some *relative* links are broken and the 3.9 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/clirr-report.html
> 
> JApiCmp Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-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:
> 
> git clone https://gitbox.apache.org/repos/asf/lang.git -b commons-lang-3.9-RC1
> cd commons-lang-3.9-RC1
> 
> 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 t

Re: [lang] Remove final modifier behaviour in java 12+ (was: Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1)

[Rob Tompkins]

I like that. I’ll get that sorted out.

-Rob

> On Apr 10, 2019, at 10:28 AM, Gary Gregory  wrote:
> 
> I think UnsupportedOperationException with a Java 12 comment, but we should
> also add @Deprecated with a comment about it not working at all on Java 12.
> 
> Gary
> 
> On Wed, Apr 10, 2019 at 8:55 AM Rob Tompkins  wrote:
> 
>> Looks like we get an exception because the final modifier isn’t removable
>> in java 12+ and for good reason [1]. So, we probably should throw an
>> exception, but both of the exceptions that arise out of the jvm here
>> https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736
>> <
>> https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736>
>> are checked exceptions. Specifically we get a “NoSuchFieldException” when
>> we attempt to retrieve “modifiers” from the “Field.” For the sake of
>> retaining BC, I would think that we would in turn convert that Exception to
>> an “UnsupportedOperationException”  or a “TypeNotPresentException” (maybe
>> ??) for the sake of getting to an unchecked exception.
>> 
>> Open to thoughts here,
>> 
>> -Rob
>> 
>> 
>> [1]
>> http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-November/056486.html
>> 
>> 
>>> On Apr 10, 2019, at 5:09 AM, Benedikt Ritter  wrote:
>>> 
>>> Damn it, I had it on my list to fix those. Sorry, Rob!
>>> 
>>> Am Mi., 10. Apr. 2019 um 03:33 Uhr schrieb Rob Tompkins <
>> chtom...@gmail.com
>>>> :
>>> 
>>>> 
>>>> 
>>>>> On Apr 9, 2019, at 9:15 PM, Gary Gregory 
>> wrote:
>>>>> 
>>>>> +0... see Java 12 testing below.
>>>> 
>>>> That +0 is almost worth cancelling for in my opinion. I’ll wait until
>>>> tomorrow to see if anyone else wants to have an opinion here, and then
>> I’ll
>>>> have another go at it.
>>>> 
>>>> -Rob
>>>> 
>>>>> 
>>>>> Nit in the release notes: Replace "Java 8.0" with Java 8".
>>>>> 
>>>>> From the git tag, ran 'mvn -V clean package' OK for:
>>>>> 
>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>> 2018-10-24T14:41:47-04:00)
>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
>> C:\Program
>>>>> Files\Java\jdk1.8.0_202\jre
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>> "windows"
>>>>> 
>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>> 2018-10-24T14:41:47-04:00)
>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>> Java version: 11.0.2, vendor: Oracle Corporation, runtime: C:\Program
>>>>> Files\Java\openjdk\jdk-11.0.2
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>> "windows"
>>>>> 
>>>>> BUT on Java 12:
>>>>> 
>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>> 2018-10-24T14:41:47-04:00)
>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>> Java version: 12, vendor: Oracle Corporation, runtime: C:\Program
>>>>> Files\Java\openjdk\jdk-12
>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>> "windows"
>>>>> 
>>>>> I get:
>>>>> 
>>>>> [ERROR] Failures:
>>>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifier:998 expected: 
>>>> but
>>>>> was: 
>>>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifierWithAccess:1009
>> expected:
>>>>>  but was: 
>>>>> [INFO]
>>>>> [ERROR] Tests run: 5774, Failures: 2, Errors: 0, Skipped: 4
>>>>> 
>>>>> On Java 13-EA:
>>>>> 
>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>> 2018-10-24T14:41:47-04:00)
>>>>> Ma

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

[Rob Tompkins]

regory\AppData\Local\Temp\surefire5519858828807362694\surefirebooter988663828837655366.jar
>> C:\Users\ggregory\AppData\Local\Temp\surefire5519858828807362694
>> 2019-04-09T21-13-37_709-jvmRun1 surefire11717302241379819897tmp
>> surefire_07095889889312770815tmp"
>> [ERROR] Error occurred in starting fork, check output in log
>> [ERROR] Process Exit Code: 1
>> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
>> forked VM terminated without properly saying goodbye. VM crash or
>> System.exit called?
>> [ERROR] Command was cmd.exe /X /C ""C:\Program
>> Files\Java\openjdk\jdk-13\bin\java"
>> -javaagent:C:\\Users\\ggregory\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\temp\\rc\\commons-lang\\target\\jacoco.exec
>> -Xmx512m --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens
>> java.base/java.lang=ALL-UNNAMED -jar
>> C:\Users\ggregory\AppData\Local\Temp\surefire5519858828807362694\surefirebooter988663828837655366.jar
>> C:\Users\ggregory\AppData\Local\Temp\surefire5519858828807362694
>> 2019-04-09T21-13-37_709-jvmRun1 surefire11717302241379819897tmp
>> surefire_07095889889312770815tmp"
>> [ERROR] Error occurred in starting fork, check output in log
>> [ERROR] Process Exit Code: 1
>> [ERROR] at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
>> [ERROR] at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
>> [ERROR] at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
>> [ERROR] at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
>> [ERROR] at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
>> [ERROR] at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
>> [ERROR] at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
>> [ERROR] at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> [ERROR] at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
>> [ERROR] at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
>> [ERROR] at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
>> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
>> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
>> [ERROR] at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [ERROR] at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> [ERROR] at
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [ERROR] at
>> java.base/java.lang.reflect.Method.invoke(Method.java:567)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> [ERROR] at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> [ERROR]
>> [ERROR] -> [Help 1]
>> 
>> Gary
>> 
>> On Tue, Apr 9, 2019 at 3:37 PM Rob Tompkins  wrote:
>> 
>>> We have fixed quite a few bugs and added

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1

[Rob Tompkins]

> On Apr 10, 2019, at 12:25 PM, Gary Gregory  wrote:
> 
> On Wed, Apr 10, 2019 at 12:13 PM Rob Tompkins  <mailto:chtom...@gmail.com>> wrote:
> 
>> 
>> 
>>> On Apr 9, 2019, at 9:16 PM, Gary Gregory >> <mailto:garydgreg...@gmail.com>> wrote:
>>> 
>>> I also see that we are using an old version of jacoco and surefire, that
>>> probably matters…
>> 
>> Maven surefire is 3.0.0-M3. Are we willing to consume a non-release
>> version of the plugin? I ask this because I regard "-Mx”,
>> where x is a positive integer, to indicate a milestone release prior to a
>> fully fledged major release.
>> 
> 
> I am personally OK using a surefire M release in this [lang] release since:
> 
> - it still provides reproducible build
> - we are playing nice in the Maven ecosystem if report issues when we find
> them
> - we are not releasing with a snapshot reference (see point 1)

Check. -Rob

> 
> Gary
> 
> 
>>> 
>>> Gary
>>> 
>>> On Tue, Apr 9, 2019 at 9:15 PM Gary Gregory 
>> wrote:
>>> 
>>>> +0... see Java 12 testing below.
>>>> 
>>>> Nit in the release notes: Replace "Java 8.0" with Java 8".
>>>> 
>>>> From the git tag, ran 'mvn -V clean package' OK for:
>>>> 
>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>> 2018-10-24T14:41:47-04:00)
>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: C:\Program
>>>> Files\Java\jdk1.8.0_202\jre
>>>> Default locale: en_US, platform encoding: Cp1252
>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>>> 
>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>> 2018-10-24T14:41:47-04:00)
>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>> Java version: 11.0.2, vendor: Oracle Corporation, runtime: C:\Program
>>>> Files\Java\openjdk\jdk-11.0.2
>>>> Default locale: en_US, platform encoding: Cp1252
>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>>> 
>>>> BUT on Java 12:
>>>> 
>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>> 2018-10-24T14:41:47-04:00)
>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>> Java version: 12, vendor: Oracle Corporation, runtime: C:\Program
>>>> Files\Java\openjdk\jdk-12
>>>> Default locale: en_US, platform encoding: Cp1252
>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>>> 
>>>> I get:
>>>> 
>>>> [ERROR] Failures:
>>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifier:998 expected: 
>> but
>>>> was: 
>>>> [ERROR]   FieldUtilsTest.testRemoveFinalModifierWithAccess:1009
>> expected:
>>>>  but was: 
>>>> [INFO]
>>>> [ERROR] Tests run: 5774, Failures: 2, Errors: 0, Skipped: 4
>>>> 
>>>> On Java 13-EA:
>>>> 
>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>> 2018-10-24T14:41:47-04:00)
>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>> Java version: 13-ea, vendor: Oracle Corporation, runtime: C:\Program
>>>> Files\Java\openjdk\jdk-13
>>>> Default locale: en_US, platform encoding: Cp1252
>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>>> 
>>>> I get:
>>>> 
>>>> [INFO] ---
>>>> [INFO]  T E S T S
>>>> [INFO] ---
>>>> [WARNING] Corrupted STDOUT by directly writing to native stream in
>> forked
>>>> JVM 1. See FAQ web page and the dump file
>>>> 
>> C:\temp\rc\commons-lang\target\surefire-reports\2019-04-09T21-13-37_709-jvmRun1.dumpstream
>>>> [INFO]
>>>> [INFO] Results:
>>>> [INFO]
>>>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>>> [INFO]
>>>> [INFO]
>>>> 
>>>> [INFO] BUILD FAILURE
>>

Re: [commons-lang] branch master updated: LANG-1447: java 12 final modifier is no longer mutable

[Rob Tompkins]

> On Apr 10, 2019, at 2:49 PM, Gary Gregory  wrote:
> 
> The test will fail on Java 14 and above when it comes out. We do not want
> to update this method with each new release. We need a "if java is >= 12"
> test IMO.

+1

> 
> Gary
> 
> On Wed, Apr 10, 2019, 14:46  wrote:
> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> chtompki pushed a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/commons-lang.git
>> 
>> 
>> The following commit(s) were added to refs/heads/master by this push:
>> new 5f7812e  LANG-1447: java 12 final modifier is no longer mutable
>> 5f7812e is described below
>> 
>> commit 5f7812ee1c2f583e1a1902c96b5b519e86699250
>> Author: Tompkins 
>> AuthorDate: Wed Apr 10 14:46:12 2019 -0400
>> 
>>LANG-1447: java 12 final modifier is no longer mutable
>> ---
>> src/changes/changes.xml|  2 +
>> .../apache/commons/lang3/reflect/FieldUtils.java   | 13 -
>> .../commons/lang3/reflect/FieldUtilsTest.java  | 59
>> --
>> 3 files changed, 57 insertions(+), 17 deletions(-)
>> 
>> diff --git a/src/changes/changes.xml b/src/changes/changes.xml
>> index 6138bd4..4668d5b 100644
>> --- a/src/changes/changes.xml
>> +++ b/src/changes/changes.xml
>> @@ -46,6 +46,8 @@ The  type attribute can be add,update,fix,remove.
>>   
>> 
>>   
>> +> dev="chtompki">FieldUtils.removeFinalModifier(Field, boolean), in java 12
>> +  throw exception because the final modifier is no longer
>> mutable.
>> Switch coverage
>> from cobertura to jacoco.
>> Javadoc pointing
>> to Commons RNG.
>> Add more
>> SystemUtils.IS_JAVA_XX variants.
>> diff --git
>> a/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java
>> b/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java
>> index 68146b1..99148a8 100644
>> --- a/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java
>> +++ b/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java
>> @@ -18,6 +18,7 @@ package org.apache.commons.lang3.reflect;
>> 
>> import org.apache.commons.lang3.ClassUtils;
>> import org.apache.commons.lang3.StringUtils;
>> +import org.apache.commons.lang3.SystemUtils;
>> import org.apache.commons.lang3.Validate;
>> 
>> import java.lang.annotation.Annotation;
>> @@ -712,8 +713,12 @@ public class FieldUtils {
>>  *match {@code public} fields.
>>  * @throws IllegalArgumentException
>>  * if the field is {@code null}
>> + * @deprecated As of java 12.0, we can no longer drop the
>> final modifier, thus
>> + * rendering this method obsolete. The JDK discussion
>> about this change can be found
>> + * here:
>> http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-November/056486.html
>>  * @since 3.3
>>  */
>> +@Deprecated
>> public static void removeFinalModifier(final Field field, final
>> boolean forceAccess) {
>> Validate.isTrue(field != null, "The field must not be null");
>> 
>> @@ -734,7 +739,13 @@ public class FieldUtils {
>> }
>> }
>> } catch (final NoSuchFieldException | IllegalAccessException
>> ignored) {
>> -// The field class contains always a modifiers field
>> +if (SystemUtils.IS_JAVA_12 || SystemUtils.IS_JAVA_13) {
>> +  throw new UnsupportedOperationException(
>> +  "In java 12+ final cannot be removed.",
>> +  ignored
>> +  );
>> +}
>> +// else no exception is thrown because we can modify final.
>> }
>> }
>> 
>> diff --git
>> a/src/test/java/org/apache/commons/lang3/reflect/FieldUtilsTest.java
>> b/src/test/java/org/apache/commons/lang3/reflect/FieldUtilsTest.java
>> index 8217a89..839e89d 100644
>> --- a/src/test/java/org/apache/commons/lang3/reflect/FieldUtilsTest.java
>> +++ b/src/test/java/org/apache/commons/lang3/reflect/FieldUtilsTest.java
>> @@ -18,6 +18,7 @@ package org.apache.commons.lang3.reflect;
>> 
>> import org.apache.commons.lang3.ArrayUtils;
>> 
>> +import org.apache.commons.lang3.SystemUtils;
>> import org.apache.commons.lang3.reflect.testbed.Ambig;
>> import org.apache.commons.lang3.reflect.testbed.Annotated;
>> import org.apache.commons.lang3.reflect.testbed.Foo;
>> @@ -43,6 +44,7 @@ import static
>> org.junit.jupiter.api.Assertions.assertNotNull;
>> import static org.junit.jupiter.api.Assertions.assertNull;
>> import static org.junit.jupiter.api.Assertions.assertThrows;
>> import static org.junit.jupiter.api.Assertions.assertTrue;
>> +import static org.junit.jupiter.api.Assertions.fail;
>> import static org.junit.jupiter.api.Assumptions.assumeTrue;
>> 
>> /**
>> @@ -993,10 +995,11 @@ public class FieldUtilsTest {
>> final Field field =
>> StaticContainer.class.getDeclaredField("IMMUTABLE_PRIVATE_2");
>> assertFalse(field.isAccessible());
>> assertTrue(Modifier.isFinal(field.getModifiers()));

Re: [BCEL] Console warning

[Rob Tompkins]

> On Apr 10, 2019, at 7:20 PM, Gary Gregory  wrote:
> 
> Hi All:
> 
> In BCEL, we log a warning to the console:
> 
> https://github.com/apache/commons-bcel/blob/master/src/main/java/org/apache/bcel/classfile/Attribute.java#L240
> 
> Which you can't really do anything about since it does not tell you what
> class file it is complaining about.
> 
> 1) Should remove the logging?

Uncertain here. In the general case, I feel like we should either do nothing or 
throw an exception. But the logic feels like it warrants some explanation, so I 
don’t know

> or,
> 2) Should we improve the logging?

This should be our minimal plan, if removing it doesn’t make sense.

> or,
> 3) Do nothing?

Because you brought it up, it feels like something should be done?

> 
> Gary

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [BCEL] Console warning

[Rob Tompkins]

> On Apr 10, 2019, at 7:46 PM, Gary Gregory  wrote:
> 
>> On Wed, Apr 10, 2019 at 7:44 PM Rob Tompkins  wrote:
>> 
>> 
>> 
>>> On Apr 10, 2019, at 7:20 PM, Gary Gregory 
>> wrote:
>>> 
>>> Hi All:
>>> 
>>> In BCEL, we log a warning to the console:
>>> 
>>> 
>> https://github.com/apache/commons-bcel/blob/master/src/main/java/org/apache/bcel/classfile/Attribute.java#L240
>>> 
>>> Which you can't really do anything about since it does not tell you what
>>> class file it is complaining about.
>>> 
>>> 1) Should remove the logging?
>> 
>> Uncertain here. In the general case, I feel like we should either do
>> nothing or throw an exception. But the logic feels like it warrants some
>> explanation, so I don’t know
>> 
>>> or,
>>> 2) Should we improve the logging?
>> 
>> This should be our minimal plan, if removing it doesn’t make sense.
>> 
>>> or,
>>> 3) Do nothing?
>> 
>> Because you brought it up, it feels like something should be done?
>> 
> 
> I see these possible solutions:
> 
> 1) Remove the logging (simple)
> 2) Make logging configurable (bleh)
> 3) Use a logging API (Log4j 2 for example)
> 4) Throw an exception in the next major version if this is _really_ an
> incorrect state but that does not seem like it would help anyone.
> 
> I favor (1).

+1, particularly with Mark’s context. -Rob
> 
> Gary
> 
> 
>>> 
>>> Gary
>> 
>> -
>> 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

[VOTE] Release Apache Commons Lang 3.9 based on RC2

[Rob Tompkins]

We have fixed quite a few bugs and added some significant enhancements since 
Apache Commons Lang 3.8.1 was released, so I would like to release Apache 
Commons Lang 3.9.

Apache Commons Lang 3.9 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2 (svn revision 
33558)
   
The Git tag commons-lang-3.9-RC2 commit for this RC is 
abb39c22c0e538fff03ea4e53d78ee60c6c08092 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=abb39c22c0e538fff03ea4e53d78ee60c6c08092
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch 
commons-lang-3.9-RC2

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1434/org/apache/commons/commons-lang3/3.9/

These are the Maven artifacts and their hashes in Nexus:

#Nexus SHA-1s
commons-lang3-3.9-sources.jar=8f1cb192e229bc4cd1c900c51171d96706e6d195
commons-lang3-3.9.pom=2b7f0896fc2f13bbe7b0022c85738e3b6a3f201a
commons-lang3-3.9.jar=0122c7cee69b53ed4a7681c03d4ee4c0e2765da5
commons-lang3-3.9-tests.jar=611d1375aed0bbacc28f88e5c80bf156a5167d09
commons-lang3-3.9-test-sources.jar=82db03243e6a388c9a2d6a061e847fb25f673051

#Release SHA-512s
#Wed Apr 10 21:30:38 EDT 2019
commons-lang3-3.9-src.tar.gz=bf69e747a2ed1a0a1b67e5c0e7bdb2344f7d8b0a88e0b535d8bdee627cbdc7be769593b58b76c84149acbb6f284f9b125095ba5a9d222413c033d1b72e07ac98
commons-lang3-3.9-src.zip=e4de802a3889451c35c60336134089980d8d1f08f02625b3b7f3f157349b8d659cd1159ffdf57f29f15277340a015375d9c4bdfade51535bc76ace0f0d107470
commons-lang3-3.9-bin.tar.gz=f9c76b0848e28bd230cd034aff9f632da0548659461dcf5c7d34a7fcab15f031b6fece1f5096661336362b1a23b8bd899a2b14a32e91b2ac5fa27e4e7a489288
commons-lang3-3.9-bin.zip=0a868109016e1d06934b5ab556b5bfff0a060e415cc8261689225a494a80230afce4524876d04b0898068d8bb0d46a36d427811fd1441a1e32d4977e1fe7605a



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: 11.0.2, vendor: Amazon.com Inc., runtime: 
/Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac"


Details of changes since 3.8.1 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site
(note some *relative* links are broken and the 3.9 directories are not yet 
created - these will be OK once the site is deployed.)

CLIRR Report (compared to 3.8.1):

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/clirr-report.html

JApiCmp Report (compared to 3.8.1):

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/lang/3.9-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/lang.git -b commons-lang-3.9-RC2
cd commons-lang-3.9-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

Re: Link from github to gitbox broken

[Rob Tompkins]

Something seems to be awry with gitbox (generally??). -Rob

> On Apr 11, 2019, at 11:21 AM, Gary Gregory  wrote:
> 
> The merge I just did in
> 
> https://github.com/apache/commons-vfs/
> 
> for
> 
> https://github.com/apache/commons-vfs/commit/7def2938b14845e6d095ae82e6db8efe6ff8e24a
> 
> 
> is not reflected in
> 
> https://gitbox.apache.org/repos/asf?p=commons-vfs.git
> 
> Thoughts?
> 
> Gary


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [lang] Remove final modifier behaviour in java 12+ (was: Re: [VOTE] Release Apache Commons Lang 3.9 based on RC1)

[Rob Tompkins]

That’s what I switched to. -Rob

> On Apr 11, 2019, at 2:44 PM, Benedikt Ritter  wrote:
> 
> An alternative would be to use SystemUtils.isJavaVersionAtMost the have
> behavior depending on the current Java versions. This would preserve the
> behavior for users on Java < 12.
> 
> Benedikt
> 
> Am Mi., 10. Apr. 2019 um 16:32 Uhr schrieb Rob Tompkins > :
> 
>> I like that. I’ll get that sorted out.
>> 
>> -Rob
>> 
>>> On Apr 10, 2019, at 10:28 AM, Gary Gregory 
>> wrote:
>>> 
>>> I think UnsupportedOperationException with a Java 12 comment, but we
>> should
>>> also add @Deprecated with a comment about it not working at all on Java
>> 12.
>>> 
>>> Gary
>>> 
>>>> On Wed, Apr 10, 2019 at 8:55 AM Rob Tompkins  wrote:
>>>> 
>>>> Looks like we get an exception because the final modifier isn’t
>> removable
>>>> in java 12+ and for good reason [1]. So, we probably should throw an
>>>> exception, but both of the exceptions that arise out of the jvm here
>>>> 
>> https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736
>>>> <
>>>> 
>> https://github.com/apache/commons-lang/blob/master/src/main/java/org/apache/commons/lang3/reflect/FieldUtils.java#L736
>>> 
>>>> are checked exceptions. Specifically we get a “NoSuchFieldException”
>> when
>>>> we attempt to retrieve “modifiers” from the “Field.” For the sake of
>>>> retaining BC, I would think that we would in turn convert that
>> Exception to
>>>> an “UnsupportedOperationException”  or a “TypeNotPresentException”
>> (maybe
>>>> ??) for the sake of getting to an unchecked exception.
>>>> 
>>>> Open to thoughts here,
>>>> 
>>>> -Rob
>>>> 
>>>> 
>>>> [1]
>>>> 
>> http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-November/056486.html
>>>> 
>>>> 
>>>>> On Apr 10, 2019, at 5:09 AM, Benedikt Ritter 
>> wrote:
>>>>> 
>>>>> Damn it, I had it on my list to fix those. Sorry, Rob!
>>>>> 
>>>>> Am Mi., 10. Apr. 2019 um 03:33 Uhr schrieb Rob Tompkins <
>>>> chtom...@gmail.com
>>>>>> :
>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On Apr 9, 2019, at 9:15 PM, Gary Gregory 
>>>> wrote:
>>>>>>> 
>>>>>>> +0... see Java 12 testing below.
>>>>>> 
>>>>>> That +0 is almost worth cancelling for in my opinion. I’ll wait until
>>>>>> tomorrow to see if anyone else wants to have an opinion here, and then
>>>> I’ll
>>>>>> have another go at it.
>>>>>> 
>>>>>> -Rob
>>>>>> 
>>>>>>> 
>>>>>>> Nit in the release notes: Replace "Java 8.0" with Java 8".
>>>>>>> 
>>>>>>> From the git tag, ran 'mvn -V clean package' OK for:
>>>>>>> 
>>>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>>>> 2018-10-24T14:41:47-04:00)
>>>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>>>> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
>>>> C:\Program
>>>>>>> Files\Java\jdk1.8.0_202\jre
>>>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>>>> "windows"
>>>>>>> 
>>>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
>>>>>>> 2018-10-24T14:41:47-04:00)
>>>>>>> Maven home: C:\Java\apache-maven-3.6.0\bin\..
>>>>>>> Java version: 11.0.2, vendor: Oracle Corporation, runtime: C:\Program
>>>>>>> Files\Java\openjdk\jdk-11.0.2
>>>>>>> Default locale: en_US, platform encoding: Cp1252
>>>>>>> OS name: "windows 10", version: "10.0", arch: "amd64", family:
>>>> "windows"
>>>>>>> 
>>>>>>> BUT on Java 12:
>>>>>>> 
>>>>>>> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb2

Re: [crypto] Can somebody have a look at my PR?

[Rob Tompkins]

> On Apr 13, 2019, at 3:30 PM, Alex Remily  wrote:
> 
> Commons Crypto Committer Team,
> 
> Please have a look at my PR when you get a chance.  Fixes the Windows build
> and includes support for OpenSSL 1.1.

I’ll try to give it a read this evening. 

-Rob

> 
> https://github.com/apache/commons-crypto/pull/94
> 
> Thanks,
> 
> Alex

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Lang 3.9 based on RC2

[Rob Tompkins]

Here’s my +1

Anyone else want to give it a look? If I don’t hear in the next few hours, I’ll 
tally the [RESULT]. 

Cheers,
-Rob

> On Apr 10, 2019, at 9:41 PM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Lang 3.8.1 was released, so I would like to release Apache 
> Commons Lang 3.9.
> 
> Apache Commons Lang 3.9 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2 (svn revision 
> 33558)
> 
> The Git tag commons-lang-3.9-RC2 commit for this RC is 
> abb39c22c0e538fff03ea4e53d78ee60c6c08092 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=abb39c22c0e538fff03ea4e53d78ee60c6c08092
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch 
> commons-lang-3.9-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1434/org/apache/commons/commons-lang3/3.9/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus SHA-1s
> commons-lang3-3.9-sources.jar=8f1cb192e229bc4cd1c900c51171d96706e6d195
> commons-lang3-3.9.pom=2b7f0896fc2f13bbe7b0022c85738e3b6a3f201a
> commons-lang3-3.9.jar=0122c7cee69b53ed4a7681c03d4ee4c0e2765da5
> commons-lang3-3.9-tests.jar=611d1375aed0bbacc28f88e5c80bf156a5167d09
> commons-lang3-3.9-test-sources.jar=82db03243e6a388c9a2d6a061e847fb25f673051
> 
> #Release SHA-512s
> #Wed Apr 10 21:30:38 EDT 2019
> commons-lang3-3.9-src.tar.gz=bf69e747a2ed1a0a1b67e5c0e7bdb2344f7d8b0a88e0b535d8bdee627cbdc7be769593b58b76c84149acbb6f284f9b125095ba5a9d222413c033d1b72e07ac98
> commons-lang3-3.9-src.zip=e4de802a3889451c35c60336134089980d8d1f08f02625b3b7f3f157349b8d659cd1159ffdf57f29f15277340a015375d9c4bdfade51535bc76ace0f0d107470
> commons-lang3-3.9-bin.tar.gz=f9c76b0848e28bd230cd034aff9f632da0548659461dcf5c7d34a7fcab15f031b6fece1f5096661336362b1a23b8bd899a2b14a32e91b2ac5fa27e4e7a489288
> commons-lang3-3.9-bin.zip=0a868109016e1d06934b5ab556b5bfff0a060e415cc8261689225a494a80230afce4524876d04b0898068d8bb0d46a36d427811fd1441a1e32d4977e1fe7605a
> 
> 
> 
> 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: 11.0.2, vendor: Amazon.com Inc., runtime: 
> /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac"
> 
> 
> Details of changes since 3.8.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site
>(note some *relative* links are broken and the 3.9 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/clirr-report.html
> 
> JApiCmp Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-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/lang.git -b commons-lang-3.9-RC2
> cd commons-lang-3.9-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

[RESULT][VOTE] Release Apache Commons Lang 3.9 based on RC2

[Rob Tompkins]

This vote passes with +1s from:

Bruno Kinoshita: +1,
Gary Gregory: +1,
Rob Tompkins: +1.

I will proceed with the release process.

Many thanks,
-Rob

> On Apr 10, 2019, at 9:41 PM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons Lang 3.8.1 was released, so I would like to release Apache 
> Commons Lang 3.9.
> 
> Apache Commons Lang 3.9 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2 (svn revision 
> 33558)
> 
> The Git tag commons-lang-3.9-RC2 commit for this RC is 
> abb39c22c0e538fff03ea4e53d78ee60c6c08092 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=abb39c22c0e538fff03ea4e53d78ee60c6c08092
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch 
> commons-lang-3.9-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1434/org/apache/commons/commons-lang3/3.9/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus SHA-1s
> commons-lang3-3.9-sources.jar=8f1cb192e229bc4cd1c900c51171d96706e6d195
> commons-lang3-3.9.pom=2b7f0896fc2f13bbe7b0022c85738e3b6a3f201a
> commons-lang3-3.9.jar=0122c7cee69b53ed4a7681c03d4ee4c0e2765da5
> commons-lang3-3.9-tests.jar=611d1375aed0bbacc28f88e5c80bf156a5167d09
> commons-lang3-3.9-test-sources.jar=82db03243e6a388c9a2d6a061e847fb25f673051
> 
> #Release SHA-512s
> #Wed Apr 10 21:30:38 EDT 2019
> commons-lang3-3.9-src.tar.gz=bf69e747a2ed1a0a1b67e5c0e7bdb2344f7d8b0a88e0b535d8bdee627cbdc7be769593b58b76c84149acbb6f284f9b125095ba5a9d222413c033d1b72e07ac98
> commons-lang3-3.9-src.zip=e4de802a3889451c35c60336134089980d8d1f08f02625b3b7f3f157349b8d659cd1159ffdf57f29f15277340a015375d9c4bdfade51535bc76ace0f0d107470
> commons-lang3-3.9-bin.tar.gz=f9c76b0848e28bd230cd034aff9f632da0548659461dcf5c7d34a7fcab15f031b6fece1f5096661336362b1a23b8bd899a2b14a32e91b2ac5fa27e4e7a489288
> commons-lang3-3.9-bin.zip=0a868109016e1d06934b5ab556b5bfff0a060e415cc8261689225a494a80230afce4524876d04b0898068d8bb0d46a36d427811fd1441a1e32d4977e1fe7605a
> 
> 
> 
> 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: 11.0.2, vendor: Amazon.com Inc., runtime: 
> /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac"
> 
> 
> Details of changes since 3.8.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/changes-report.html
> 
> Site:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site
>(note some *relative* links are broken and the 3.9 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/clirr-report.html
> 
> JApiCmp Report (compared to 3.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-RC2/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.9-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/lang.git -b commons-lang-3.9-RC2
> cd commons-lang-3.9-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

Re: Nexus: Promotion Completed

[Rob Tompkins]

This isn’t our release plugin generating all these signatures. I’m not entirely 
sure what’s going on here, but it's clearly something silly.

I’ll put this on the TODO list….feels like a COMMONSSITE jira right?

-Rob


> On Apr 14, 2019, at 6:47 PM, Nexus Repository Manager 
>  wrote:
> 
> Message from: https://repository.apache.org <https://repository.apache.org/>
> 
> Description:
> 
> Promote commons-lang3-3.9 from RC2
> 
> 
> 
> Deployer properties:
> "userAgent" = "Apache-Maven/3.6.0 (Java 11.0.2; Mac OS X 10.14.4)"
> "userId" = "chtompki"
> "ip" = "71.63.111.103"
> 
> Details:
> 
> The following artifacts have been promoted to the "Releases" [id=releases] 
> <https://repository.apache.org/content/repositories/releases> repository
> 
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar.asc.asc
>  
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar.asc.asc>
> (SHA1: a324db96c6c0a4c39d8fbc9f4bafb87697da3144)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar.asc.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar.asc.asc>
> (SHA1: 926e87c8f49b7fa07ee3db2f6add0816a8e8c45a)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar.asc>
> (SHA1: 2fb9b4ec04a24b80f815ae0934f85de3cfbcf384)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar>
> (SHA1: 8f1cb192e229bc4cd1c900c51171d96706e6d195)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom>
> (SHA1: 2b7f0896fc2f13bbe7b0022c85738e3b6a3f201a)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar>
> (SHA1: 0122c7cee69b53ed4a7681c03d4ee4c0e2765da5)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom.asc>
> (SHA1: 3798818d3cc619fbc30de2a233c060d7ab6091c0)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar.asc>
> (SHA1: 495ed9d8d7b4b3d75a4a0c4bf025177934cd7692)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom.asc.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.pom.asc.asc>
> (SHA1: f59d50e20d0e3397107af01e9acca67170c1148d)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar>
> (SHA1: 611d1375aed0bbacc28f88e5c80bf156a5167d09)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar.asc>
> (SHA1: 18da28f66501bc0ea56ce72fd2ae1b7c37522846)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-test-sources.jar>
> (SHA1: 82db03243e6a388c9a2d6a061e847fb25f673051)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar.asc.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-tests.jar.asc.asc>
> (SHA1: 828f75e983258cf8454b4b05d7463fa8584f)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9.jar.asc>
> (SHA1: 080dfe53cf1f78275a9c91d231a7ab1f799f5a20)
> /org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar.asc.asc 
> <https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-lang3/3.9/commons-lang3-3.9-sources.jar.asc.asc>
> (SHA1: 2b20d099aca6f0b37471b797b3099062063ca90f)
> 
> Action performed by Rob Tompkins (chtompki)

[ANN] Apache Commons Lang 3.9 released

[Rob Tompkins]

The Apache Commons community is happy to announce the availability of Apache
Commons Lang 3.9.

Apache Commons Lang provides helper utilities for the java.lang API, notably
String manipulation methods, basic numerical methods, object reflection,
concurrency, creation and serialization and System properties. Additionally it
contains basic enhancements to java.util.Date and a series of utilities
dedicated to help with building methods, such as hashCode, toString and equals.

For more details see the release notes at:
http://www.apache.org/dist/commons/lang/RELEASE-NOTES.txt

Distribution packages can be downloaded from:
https://commons.apache.org/proper/commons-lang/download_lang.cgi

When downloading, please verify signatures using the KEYS file available at:
http://www.apache.org/dist/commons

Maven artifacts are also available in the central Maven repository:


  org.apache.commons
  commons-lang3
  3.9


Best regards,
Rob Tompkins
on behalf of the Apache Commons community
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [compress] Java 7 to Java 8

[Rob Tompkins]

> On Apr 16, 2019, at 8:31 AM, Gary Gregory  wrote:
> 
> Hi All:
> 
> Based on a recent JIRA, it seems like using Java 8 in [compress] would be
> helpful. Plus, it's 2019 and Java 12 is out.

+1


> 
> Gary

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Build failed in Jenkins: commons-lang #517

[Rob Tompkins]

Oh…I can fix this super quick. I’ll delete what’s in staging and it’ll work.

-Rob

> On Apr 16, 2019, at 10:46 AM, sebb  wrote:
> 
> On Tue, 16 Apr 2019 at 14:43, Gary Gregory  > wrote:
>> 
>> Is this a credentials issue in Jenkins or an issue with our release plugin?
>> 
>> Why are we even invoking our release plugin here?
> 
> The profile -Prelease may have something to do with that.
> 
>> Gary
>> 
>> -- Forwarded message -
>> From: Apache Jenkins Server 
>> Date: Tue, Apr 16, 2019 at 9:18 AM
>> Subject: Build failed in Jenkins: commons-lang #517
>> To: 
>> 
>> 
>> See <
>> https://builds.apache.org/job/commons-lang/517/display/redirect?page=changes
>>> 
>> 
>> Changes:
>> 
>> [gardgregory] Add OpenJDK 8 to Travis builds.
>> 
>> --
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building remotely on H22 (ubuntu xenial) in workspace <
>> https://builds.apache.org/job/commons-lang/ws/>
>> No credentials specified
>> Cloning the remote Git repository
>> Cloning repository https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git init  # timeout=10
>> Fetching upstream changes from
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git --version # timeout=10
>>> git fetch --tags --progress
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>> +refs/heads/*:refs/remotes/origin/*
>>> git config remote.origin.url
>> https://gitbox.apache.org/repos/asf/commons-lang.git # timeout=10
>>> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
>> # timeout=10
>>> git config remote.origin.url
>> https://gitbox.apache.org/repos/asf/commons-lang.git # timeout=10
>> Fetching upstream changes from
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git fetch --tags --progress
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>> +refs/heads/*:refs/remotes/origin/*
>>> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>>> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>> Checking out Revision 7964c45a54347dcdcd9ea1640c62dac7b3d71809
>> (refs/remotes/origin/master)
>>> git config core.sparsecheckout # timeout=10
>>> git checkout -f 7964c45a54347dcdcd9ea1640c62dac7b3d71809
>> Commit message: "Add OpenJDK 8 to Travis builds."
>>> git rev-list --no-walk f2c28e67b7c883db33a6cd1f7aba154b79f73d5b #
>> timeout=10
>> Parsing POMs
>> Downloaded artifact
>> http://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/48/commons-parent-48.pom
>> Established TCP socket on 44520
>> maven35-agent.jar already up to date
>> maven35-interceptor.jar already up to date
>> maven3-interceptor-commons.jar already up to date
>> [commons-lang] $ /home/jenkins/tools/java/latest1.8/bin/java -Xmx4g -Xms4g
>> -cp
>> /home/jenkins/jenkins-slave/maven35-agent.jar:/home/jenkins/tools/maven/latest/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest/conf/logging
>> jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/latest/
>> /home/jenkins/jenkins-slave/remoting.jar
>> /home/jenkins/jenkins-slave/maven35-interceptor.jar
>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 44520
>> <===[JENKINS REMOTING CAPACITY]===>   channel started
>> Executing Maven:  -B -f <
>> https://builds.apache.org/job/commons-lang/ws/pom.xml>
>> -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1 clean
>> install javadoc:javadoc --batch-mode -Dgpg.skip -Prelease
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO] --< org.apache.commons:commons-lang3
>>> --
>> [INFO] Building Apache Commons Lang 3.10-SNAPSHOT
>> [INFO] [ jar
>> ]-
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.pom
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.pom
>> (6.7 kB at 26 kB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.jar
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.jar
>> (27 kB at 1.4 MB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.pom
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.pom
>> (28 kB at 1.5 MB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.jar
>> [INFO] Downloaded from central:
>> 

Re: Build failed in Jenkins: commons-lang #517

[Rob Tompkins]

Pardon my missing that….was traveling quite hard yesterday. (Day trip to 
California) -Rob

> On Apr 16, 2019, at 10:46 AM, sebb  wrote:
> 
> On Tue, 16 Apr 2019 at 14:43, Gary Gregory  > wrote:
>> 
>> Is this a credentials issue in Jenkins or an issue with our release plugin?
>> 
>> Why are we even invoking our release plugin here?
> 
> The profile -Prelease may have something to do with that.
> 
>> Gary
>> 
>> -- Forwarded message -
>> From: Apache Jenkins Server 
>> Date: Tue, Apr 16, 2019 at 9:18 AM
>> Subject: Build failed in Jenkins: commons-lang #517
>> To: 
>> 
>> 
>> See <
>> https://builds.apache.org/job/commons-lang/517/display/redirect?page=changes
>>> 
>> 
>> Changes:
>> 
>> [gardgregory] Add OpenJDK 8 to Travis builds.
>> 
>> --
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building remotely on H22 (ubuntu xenial) in workspace <
>> https://builds.apache.org/job/commons-lang/ws/>
>> No credentials specified
>> Cloning the remote Git repository
>> Cloning repository https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git init  # timeout=10
>> Fetching upstream changes from
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git --version # timeout=10
>>> git fetch --tags --progress
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>> +refs/heads/*:refs/remotes/origin/*
>>> git config remote.origin.url
>> https://gitbox.apache.org/repos/asf/commons-lang.git # timeout=10
>>> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
>> # timeout=10
>>> git config remote.origin.url
>> https://gitbox.apache.org/repos/asf/commons-lang.git # timeout=10
>> Fetching upstream changes from
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>>> git fetch --tags --progress
>> https://gitbox.apache.org/repos/asf/commons-lang.git
>> +refs/heads/*:refs/remotes/origin/*
>>> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>>> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>> Checking out Revision 7964c45a54347dcdcd9ea1640c62dac7b3d71809
>> (refs/remotes/origin/master)
>>> git config core.sparsecheckout # timeout=10
>>> git checkout -f 7964c45a54347dcdcd9ea1640c62dac7b3d71809
>> Commit message: "Add OpenJDK 8 to Travis builds."
>>> git rev-list --no-walk f2c28e67b7c883db33a6cd1f7aba154b79f73d5b #
>> timeout=10
>> Parsing POMs
>> Downloaded artifact
>> http://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/48/commons-parent-48.pom
>> Established TCP socket on 44520
>> maven35-agent.jar already up to date
>> maven35-interceptor.jar already up to date
>> maven3-interceptor-commons.jar already up to date
>> [commons-lang] $ /home/jenkins/tools/java/latest1.8/bin/java -Xmx4g -Xms4g
>> -cp
>> /home/jenkins/jenkins-slave/maven35-agent.jar:/home/jenkins/tools/maven/latest/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest/conf/logging
>> jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/latest/
>> /home/jenkins/jenkins-slave/remoting.jar
>> /home/jenkins/jenkins-slave/maven35-interceptor.jar
>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 44520
>> <===[JENKINS REMOTING CAPACITY]===>   channel started
>> Executing Maven:  -B -f <
>> https://builds.apache.org/job/commons-lang/ws/pom.xml>
>> -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1 clean
>> install javadoc:javadoc --batch-mode -Dgpg.skip -Prelease
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO] --< org.apache.commons:commons-lang3
>>> --
>> [INFO] Building Apache Commons Lang 3.10-SNAPSHOT
>> [INFO] [ jar
>> ]-
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.pom
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.pom
>> (6.7 kB at 26 kB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.jar
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.1/maven-jar-plugin-3.1.1.jar
>> (27 kB at 1.4 MB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.pom
>> [INFO] Downloaded from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.pom
>> (28 kB at 1.5 MB/s)
>> [INFO] Downloading from central:
>> https://repo.maven.apache.org/maven2/org/apache/commons/commons-release-plugin/1.6/commons-release-plugin-1.6.jar
>> [INFO] Downloaded from cent

Re: [ALL] Confluence Wiki permissions - allow all Commons committers write access?

[Rob Tompkins]

> On Apr 17, 2019, at 11:16 AM, sebb  wrote:
> 
> Confluence supports LDAP member attributes only [1] currently.
> 
> This means we could automatically grant access to Commons committers.
> However it's not currently possible to restrict access to PMC members
> - but I'm not sure that we need that.
> 
> I propose to ask Infra to allow Commons committer write access to the Wiki.
> 
> Agreed?

+1

> 
> [Administrators can always grant write access to individual
> non-committers if that proves necessary.]
> 
> Sebb.
> [1] 
> https://lists.apache.org/thread.html/33d84ab4720f56827895b9cac6743943c0bfe1af2f838cdab2a026d4@%3Cusers.infra.apache.org%3E
> 
> -
> 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

Re: [VOTE] Release Apache Commons Imaging 1.0-alpha1 based on RC3

[Rob Tompkins]

+1 

builds on java8, one test fails on java 11:  
DataParserIndexedTest.testFailsToCreateDataParserIndexedThrowsArrayIndexOutOfBoundsException:33
 expected:<[256]> but was:<[Index 256 out of bounds for length 24]>

Signatures all ok, rat ok, minor nits in the reports (nothing particularly 
noteworthy).



> On Apr 27, 2019, at 8:22 AM, Bruno P. Kinoshita  wrote:
> 
> I would like to release Apache Commons Imaging 1.0-alpha1.
> 
> Apache Commons Imaging 1.0-alpha1 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha1-RC3 
> (svn revision 33801)
> 
> The Git tag commons-imaging-1.0-alpha1-RC3 commit for this RC is 
> 6f04ccc2cf8c867298579c355c6d88fd74da3e7b which you can browse here:
> 
> https://git-wip-us.apache.org/repos/asf?p=commons-imaging.git;a=tag;h=refs/tags/commons-imaging-1.0-alpha1-RC3
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1438/org/apache/commons/commons-imaging/1.0-alpha1/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> ${commons.sha256list}
> #Release SHA-512s
> #Sat Apr 27 23:40:11 NZST 2019
> commons-imaging-1.0-alpha1-sources-java-source=320ed4dae9045e38f4956558b38497593de35197051e6370cc5d959782e191ec40cbdf651cc0e5dfe62afd25d9fbad0dc73ff3db4a914757a058f1b88570a649
> commons-imaging-1.0-alpha1-bin-zip=699124772e2ad47be85230fa6529eb710a26567c416e5d950445a637b426f86c3ad1c9577f41f7e2f6bd94016b14192077ba3305a85ff36601ca36703a935eb7
> commons-imaging-1.0-alpha1-sources-jar.asc=2e8445b62c1a4afbbae0f7ccdd97d18f2ba2db57c5be649c089a70bce70e816c55422241ee44040ee3122bae45f05c664bf07764446a72b623272dc540cb255b
> commons-imaging-1.0-alpha1-src-zip.asc=21acf6132380c42c6823f599ff6c31900868ac5131837ed17c9c40c7e99d3b88410a2d5331b922da605f54a9cf68ff70d705d3ca94cd6db7a4f9b5d0a9e1c3ee
> commons-imaging-1.0-alpha1-pom.asc=38d13c75c3f134b39b31a8e6ad563e921bd9a7ad8008dd78854999841463a45ca98c52547b84657cb7700725bf683c22bf925be898107a4ce7c6d0f35ee83c61
> commons-imaging-1.0-alpha1-tests-jar.asc=6f800eaaf02550e3b13d459b2e8885f5bf5b3bed02611997cf6c35fb782ef5a634eb21c907d046167778df6a3cfbd948c9cb464a34da88813ce08ccd5ebba386
> commons-imaging-1.0-alpha1-javadoc-jar.asc=7c562516e9f88b7490b7123fc529d5dc33303453c5990bcf23ecfc9ca46fc6df5324c3cdc5bf49bfa4e7d3de49d80591d97721df6890369cdbf95aba700d577f
> commons-imaging-1.0-alpha1-tests-test-jar=58a9ac4861a70a87d3490d09e2d90e6ef0293711a9edf3f7fab10776e9d37484c421f4be283531aa6985abbac474604e0f633442b509e0b1ccef1a95a788c754
> commons-imaging-1.0-alpha1-jar.asc=18a007c1185de84b3395b1d8b2e1e1c466939020646c015fca29be4fc1d9647ec4d8afcc20bf562bfdae01d740b0117bd3b904fd022b7d6e944569c78517adc5
> commons-imaging-1.0-alpha1-bin-tar.gz.asc=31995c5e035a753d86294f90850de1d73fef478a6bb234cebab6272b9c5521dcb1e5ec3a180508929e765f18af4202dbbe616b0264f7ab50c40be793cca1
> commons-imaging-1.0-alpha1-test-sources-jar.asc=6f3265c73f2f3b4d67b4d084f2e309032591fdbd25b40b93cb854d8f9c61a719bc27b3de37ed5faf36caed295a944f1e48399e1120b55f307d9bb842b965d5b7
> commons-imaging-1.0-alpha1-src-tar.gz=3c06195e75161e5bf2364f358169a2cd9231c8c30c526c060efa7d8972394ddcdb2bc2a9caa64073700e2c7eabf0830ccd33a84defafc72a444889a579e86073
> commons-imaging-1.0-alpha1-bin-zip.asc=69dbfbb5f2aa2a85ae87c4510777643706214dec171c87b1ee992b5f5caab9401ef32ad54dcaf2e590a8cf694a9bb89d0e335c13fff0a95dc402454b287b99a6
> commons-imaging-1.0-alpha1-javadoc-javadoc=7cde692d47ce4f2936803b9c8d54ad7c71a070507d6c8fd4533421d43fc019908e24ade7264b01080e1c614d26c71454237a000fb81a464e83907d35b6450730
> commons-imaging-1.0-alpha1-src-zip=8eea523c614561b7da7c1e3203a0c48f1d3fdcaaf178e843c7834ff6b546ee7f09270385558adc16583bd1cd6e6d953a3b67ffcf117727bb7ad1b45d9b546a4a
> commons-imaging-1.0-alpha1-bin-tar.gz=f7ac881d8439007d1b4f0ba83df3da75ebdc2b2b0e7632762cb0ad9e5ec57f6553ae72223a1d91c30cc7035dfd28009d778653f18fc5476cf27fc040f1df717f
> commons-imaging-1.0-alpha1-test-sources-java-source=16cea0d32ae8a9da68d8bafa52a1519c5a9f20dd3097acb5826ddcc6364747af01d81b76b12c3ce9e40da049f3a2aaa78259ac7ea57ea8334c3f79c42cb75aae
> commons-imaging-1.0-alpha1-src-tar.gz.asc=cdb66c75cdf944756ff857422c3f1172832abc0889ef501f0ee7f925643470beea1304c9f7782beb089e77c1ea65f2dc23bb2dc37f756dec5f8d5d52c83d9e01
> 
> 
> (no need for .asc hashes!)
> 
> I have tested this with ***'mvn clean install site'*** using: 
> 
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-18T06:33:14+12:00)
> Maven home: /opt/apache-maven-3.5.4
> Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: 
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-47-generic", arch: "amd64", family: "unix"
> 
> Details of changes are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha1-RC3/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha1-RC3/site/changes-report.html
> 
> Site:
>  

Re: [VFS] Deleting the git branch 'trunk'

[Rob Tompkins]

+1

> On Apr 29, 2019, at 10:58 AM, Otto Fowler  wrote:
> 
> +1
> 
> 
> On April 29, 2019 at 08:01:43, Gary Gregory (garydgreg...@gmail.com) wrote:
> 
> I am going to delete the branch 'trunk'.
> 
> It's too confusing.
> 
> Gary


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VFS] Deleting the git branch 'trunk'

[Rob Tompkins]

> On May 1, 2019, at 4:54 PM, Mark Thomas  wrote:
> 
>> On 01/05/2019 21:48, Gary Gregory wrote:
>>> On Wed, May 1, 2019 at 3:54 PM Gary Gregory  wrote:
>>> 
>>> I created https://issues.apache.org/jira/browse/INFRA-18316
>>> 
>> 
>> And the work is done. Note that open PRs on trunk have been closed
>> automatically, so they would need to be re-opened.
> 
> Note that as far as I can tell, the trunk branches have not been removed
> from gitbox (because trunk branches are automatically protected).
> 
> I recommend leaving them on gitbox in case someone realises in a week or
> two that there is some work on trunk that isn't anywhere else.
> 
> I suspect we can quietly forget about the trunks on gitbox but if they
> do become an issue, I can remove them from there as well.

Thanks guys. Much appreciation here.

-Rob

> 
> Mark
> 
> 
>> 
>> Gary
>> 
>> 
>>> 
>>> Gary
>>> 
>>>> On Wed, May 1, 2019 at 3:55 AM Benedikt Ritter  wrote:
>>>> 
>>>> Am Di., 30. Apr. 2019 um 14:43 Uhr schrieb Gary Gregory <
>>>> garydgreg...@gmail.com>:
>>>> 
>>>>> Should we take a broader stroke and remove ALL trunk branches from all
>>>>> Commons git repos?
>>>>> 
>>>> 
>>>> I think we should remove all trunk branches from git repos.
>>>> 
>>>> 
>>>>> 
>>>>> Gary
>>>>> 
>>>>> On Mon, Apr 29, 2019 at 11:25 AM Otto Fowler 
>>>>> wrote:
>>>>> 
>>>>>> Probably need INFRA
>>>>>> 
>>>>>> 
>>>>>> On April 29, 2019 at 11:23:38, Gary Gregory (garydgreg...@gmail.com)
>>>>>> wrote:
>>>>>> 
>>>>>> On Mon, Apr 29, 2019 at 11:22 AM Gary Gregory >>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> Well, crud, neither these works:
>>>>>>> 
>>>>>>> C:\git\commons-vfs>git push origin --delete trunk
>>>>>>> remote: Rewinding refs/heads/trunk is forbidden.
>>>>>>> remote:
>>>>>>> To https://gitbox.apache.org/repos/asf/commons-vfs
>>>>>>> ! [remote rejected] trunk (pre-receive hook declined)
>>>>>>> error: failed to push some refs to '
>>>>>>> https://gitbox.apache.org/repos/asf/commons-vfs'
>>>>>>> 
>>>>>>> C:\git\commons-vfs> git push origin :trunk
>>>>>>> remote: Rewinding refs/heads/trunk is forbidden.
>>>>>>> remote:
>>>>>>> To https://gitbox.apache.org/repos/asf/commons-vfs
>>>>>>> ! [remote rejected] trunk (pre-receive hook declined)
>>>>>>> error: failed to push some refs to '
>>>>>>> https://gitbox.apache.org/repos/asf/commons-vfs'
>>>>>>> 
>>>>>>> Thoughts?
>>>>>>> 
>>>>>> 
>>>>>> BTW, I had deleted the branch locally OK with 'git branch -d trunk'
>>>>>> 
>>>>>> Gary
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Gary
>>>>>>> 
>>>>>>> On Mon, Apr 29, 2019 at 11:11 AM Rob Tompkins 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> +1
>>>>>>>> 
>>>>>>>>> On Apr 29, 2019, at 10:58 AM, Otto Fowler <
>>>> ottobackwa...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> +1
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On April 29, 2019 at 08:01:43, Gary Gregory (
>>>> garydgreg...@gmail.com
>>>>> )
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> I am going to delete the branch 'trunk'.
>>>>>>>>> 
>>>>>>>>> It's too confusing.
>>>>>>>>> 
>>>>>>>>> Gary
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>> -
>>>>>>>> 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
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [daemon] release 1.1.1?

[Rob Tompkins]

> On May 3, 2019, at 9:18 AM, Mark Thomas  wrote:
> 
>> On 03/05/2019 13:59, Gary Gregory wrote:
>> Hi Mark and All:
>> 
>> I've seen a lot of commits lately in Daemon from Mark T.
>> 
>> Are you planning a release?
> 
> I am starting to think in that direction. There are still a handful of
> Jira issues I want to look at first.
> 
> Given past experience with the Commons release process, I'd avoid it if
> I could but that isn't an option in this case.

Let me know if you want me to do the release dirty work. I’d be happy to.

-Rob

> 
> Mark
> 
> -
> 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

Re: [daemon] release 1.1.1?

[Rob Tompkins]

> On May 3, 2019, at 9:25 AM, Mark Thomas  wrote:
> 
> On 03/05/2019 14:20, Rob Tompkins wrote:
>>> On May 3, 2019, at 9:18 AM, Mark Thomas  wrote:
>>> 
>>>> On 03/05/2019 13:59, Gary Gregory wrote:
>>>> Hi Mark and All:
>>>> 
>>>> I've seen a lot of commits lately in Daemon from Mark T.
>>>> 
>>>> Are you planning a release?
>>> 
>>> I am starting to think in that direction. There are still a handful of
>>> Jira issues I want to look at first.
>>> 
>>> Given past experience with the Commons release process, I'd avoid it if
>>> I could but that isn't an option in this case.
>> 
>> Let me know if you want me to do the release dirty work. I’d be happy to.
> 
> Thanks. I suspect I'll need to do at least the creation of the Windows
> binaries a) because of the build environment and b) because they need to
> be signed.
> 
> If you are able to answer questions as I go that will hopefully ease
> most of the pain.

Just give me a little lead time on when you’re going to head towards cutting 
the release, and I’ll make sure I’m not too far AFK.

Also, if you wanted to do things the same way as in 2017, you can. I’ve only 
tried to make things down in the “Maven Tasks” section a tad easier. 
Furthermore, the sections above would be regarding building for windows and 
such would be new to me.

-Rob

> 
> It looks like I updated the "HOWTO-RELEASE" when I did the last Daemon
> release. That should mean the only difficulties are process changes
> since ~Nov 2017.
> 
> Mark
> 
> -
> 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

Re: [bcel] broken repo?

[Rob Tompkins]

I wonder if the default branch, “trunk,” no longer exists and that’s what it’s 
trying to clone down onto. When I run the following it works:

git clone --single-branch --branch master 
https://gitbox.apache.org/repos/asf/commons-bcel.git 
<https://gitbox.apache.org/repos/asf/commons-bcel.git>

-Rob

> On May 6, 2019, at 2:05 PM, Rob Tompkins  wrote:
> 
> looking now. -Rob
> 
>> On May 6, 2019, at 1:23 PM, Gary Gregory  wrote:
>> 
>> Hi All:
>> 
>> When I try a clean checkout of BCEL I get:
>> 
>> C:\git>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
>> Cloning into 'commons-bcel'...
>> remote: Counting objects: 21585, done.
>> remote: Compressing objects: 100% (2646/2646), done.
>> Receiving objects: 100% (21585/21585), 3.83 MiB | 4.36 MiB/s, done.ing
>> objects: 100% (21585/21585), 1.25 MiB | 2.46 MiB/s
>> 
>> Resolving deltas: 100% (14986/14986), done.
>> warning: remote HEAD refers to nonexistent ref, unable to checkout.
>> 
>> Ideas?
>> 
>> Gary
> 

Re: [bcel] broken repo?

[Rob Tompkins]

looking now. -Rob

> On May 6, 2019, at 1:23 PM, Gary Gregory  wrote:
> 
> Hi All:
> 
> When I try a clean checkout of BCEL I get:
> 
> C:\git>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> Cloning into 'commons-bcel'...
> remote: Counting objects: 21585, done.
> remote: Compressing objects: 100% (2646/2646), done.
> Receiving objects: 100% (21585/21585), 3.83 MiB | 4.36 MiB/s, done.ing
> objects: 100% (21585/21585), 1.25 MiB | 2.46 MiB/s
> 
> Resolving deltas: 100% (14986/14986), done.
> warning: remote HEAD refers to nonexistent ref, unable to checkout.
> 
> Ideas?
> 
> Gary


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [numbers][GSoC] Slack for GSoC mentees

[Rob Tompkins]

> On May 6, 2019, at 2:13 PM, Udit Arora  wrote:
> 
> Congrats Ben.

+1 Congrats,  Ben. 

I think we’re trying to sort out what messaging system we’re going to use.

-Rob

> 
> On Mon, 6 May 2019, 11:42 pm Ben Nguyen,  wrote:
> 
>> Hello,
>> 
>> Any update on which communication tool will be used? Slack, Zulip? I’m
>> excited to get started!
>> 
>> Ben
>> 
>> From: Mark Thomas
>> Sent: Wednesday, May 1, 2019 4:21 PM
>> To: Commons Developers List
>> Subject: Re: [numbers][GSoC] Slack for GSoC mentees
>> 
>> On 01/05/2019 22:09, Eric Barnhill wrote:
>>> Thanks Mark,
>>> 
>>> It looks like an apache.org domain email is required to register, and I
>>> don't think my mentees are going to have one of those, so I may still
>> open
>>> a Zulip on the side. I am happy to have joined the commons slack there
>>> though!
>> 
>> You should be able to invite folks without @apache.org addresses
>> 
>> Mark
>> 
>> 
>>> 
>>> Eric
>>> 
>>> On Wed, May 1, 2019 at 1:58 PM Mark Thomas  wrote:
>>> 
 On 01/05/2019 21:54, Eric Barnhill wrote:
> On Wed, May 1, 2019 at 1:49 PM Mark Thomas  wrote:
> 
>> On 01/05/2019 21:38, Eric Barnhill wrote:
>>> Actually some objections have been raised to using Slack because it
>> is
>> not
>>> open source. So the options will be either zulipchat if a group of
 people
>>> want to use it, or Riot if it is just me.
>> 
>> Better stop using GitHub as well then.
>> 
>> There is no ASF policy that requires the tools we use to be open
>> source.
>> 
>> 
> Thanks for clarifying.
> 
> 
>> There is an ASF slack instance - you could request (create?) a
>> commons-gsoc channel there.
>> 
> 
> Knock me over with a feather. This not appear to be mentioned at
> community.apache.org .  Is it asf.slack.com?
 
 the-asf.slack.com
 There is already a commons channel. I think you can create commons-gsoc
 if you need it. If not, I look to be able to create channels. Just ping
>> me.
 
 Mark
 
 -
 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
>> 
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [bcel] broken repo?

[Rob Tompkins]

> On May 6, 2019, at 2:14 PM, sebb  wrote:
> 
> Same issue applies to commons-net and -daemon.
> However commons-io and -lang are OK.
> 
> Looks like the default branch has not been set up correctly for some
> of the repos (probably the ones that were migrated last).
> 
> How does one set the default branch?

I had to put in tickets with Infra to do that back in December/Januaray. I 
would guess that it would have something to do with their puppet automation, 
but that’s totally a guess.

-Rob

> 
> On Mon, 6 May 2019 at 19:09, Rob Tompkins  <mailto:chtom...@gmail.com>> wrote:
>> 
>> I wonder if the default branch, “trunk,” no longer exists and that’s what 
>> it’s trying to clone down onto. When I run the following it works:
>> 
>> git clone --single-branch --branch master 
>> https://gitbox.apache.org/repos/asf/commons-bcel.git 
>> <https://gitbox.apache.org/repos/asf/commons-bcel.git> 
>> <https://gitbox.apache.org/repos/asf/commons-bcel.git 
>> <https://gitbox.apache.org/repos/asf/commons-bcel.git>>
>> 
>> -Rob
>> 
>>> On May 6, 2019, at 2:05 PM, Rob Tompkins  wrote:
>>> 
>>> looking now. -Rob
>>> 
>>>> On May 6, 2019, at 1:23 PM, Gary Gregory  wrote:
>>>> 
>>>> Hi All:
>>>> 
>>>> When I try a clean checkout of BCEL I get:
>>>> 
>>>> C:\git>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
>>>> Cloning into 'commons-bcel'...
>>>> remote: Counting objects: 21585, done.
>>>> remote: Compressing objects: 100% (2646/2646), done.
>>>> Receiving objects: 100% (21585/21585), 3.83 MiB | 4.36 MiB/s, done.ing
>>>> objects: 100% (21585/21585), 1.25 MiB | 2.46 MiB/s
>>>> 
>>>> Resolving deltas: 100% (14986/14986), done.
>>>> warning: remote HEAD refers to nonexistent ref, unable to checkout.
>>>> 
>>>> Ideas?
>>>> 
>>>> Gary
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> <mailto:dev-unsubscr...@commons.apache.org>
> For additional commands, e-mail: dev-h...@commons.apache.org 
> <mailto:dev-h...@commons.apache.org>

Re: [numbers][GSoC] Slack for GSoC mentees

[Rob Tompkins]

Virendra,

Congrats. I’ve signed up to help mentor here. So it’ll be Eric as well as 
myself helping. All the best,

-Rob

> On May 6, 2019, at 2:56 PM, Virendra singh Rajpurohit 
>  wrote:
> 
> Yes, it is my preferred mail.
> 
> 
> 
> [image: Mailtrack]
> 
> Sender
> notified by
> Mailtrack
> 
> 05/07/19,
> 12:25:37 AM
> 
> 
> [image: photo]
> *Virendra Singh Rajpurohit*
> 
> +91 9760781615 | virendrasing...@gmail.com
> 
> Skype: virendrasinghrp <#>
> 
> Create your own email signature
> 
> 
> On Tue, May 7, 2019 at 12:25 AM Eric Barnhill 
> wrote:
> 
>> On Mon, May 6, 2019 at 11:51 AM Virendra singh Rajpurohit <
>> virendrasing...@gmail.com> wrote:
>> 
>>> Hey Eric, My name is there on projects list, but I haven't yet received
>> any
>>> official mail from Apache or Google.
>>> Does that mean I'm selected?
>>> 
>> 
>> 
>> Yes, congratulations you were selected. Check the spam filter maybe?
>> 
>> We've had less interaction with you, so we will need to work together
>> during community bonding to make sure you are contributing on the same
>> level as the others.
>> 
>> I will add you to the slack. Is this your preferred email?
>> 
> 
> 
> -- 
> *Virendra Singh Rajpurohit*
> 
> *University of Petroleum and Energy Studies,Dehradun*
> M:+91-9760781615
> Linkedin:https://www.linkedin.com/in/virendra-singh-rajpurohit

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [STATISTICS][Regression][Linear Math] Is there any plan/anyone working on a new Linear Math module currently?

[Rob Tompkins]

> On May 8, 2019, at 4:37 PM, Ben Nguyen  wrote:
> 
> Hello,
> 
> The regression module will require a lot of linear math, specifically matrix 
> operations which I’ve heard is outdated. Are there any updates on it’s 
> development? Is this someone’s GSoC project? If not I could try to help by 
> attempting to start porting regression essential operations. But the 
> dependencies for the current library is vast so this would end up being a 
> large endeavor and I know I am not one to properly design a linear math 
> library, I only know the basics, it would probably become a mess. So if there 
> is no current development plan I fear I might have to start by using the old 
> library for now until linear’s development kicks in…. Is this okay?
> 

I suppose the question is: what is commons-numbers, and if a matrix is a 
“number” or it is sufficiently different to warrant a separate component. 

It is worth noting that in there have been past arguments over additional math 
components before we get 1.0 releases for the current ones in flight (but I 
feel like the fastest route to any component’s 1.0 should take priority). 

What are other folks’ thoughts here? I would think that linear algebra would 
likely be a widely used library as it’s fairly fundamental to a collection of 
machine learning algorithms as they are based in least squares. 

-Rob

> Thank you,
> Ben

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [commons-rng] branch master updated: Update pom.xml

[Rob Tompkins]

> On May 8, 2019, at 6:34 PM, Gilles Sadowski  wrote:
> 
>> Le jeu. 9 mai 2019 à 00:25,  a écrit :
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> aherbert pushed a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/commons-rng.git
>> 
>> 
>> The following commit(s) were added to refs/heads/master by this push:
>> new 0996b4e  Update pom.xml
>> new 280f3ec  Merge pull request #42 from AbhishekSinghDhadwal/master
>> 0996b4e is described below
>> 
>> commit 0996b4e4292411d392e2aa86974323a58029
>> Author: Abhishek Singh Dhadwal 
>> <39513876+abhisheksinghdhad...@users.noreply.github.com>
> 
> Abhishek,
> 
> You might want to have your actual email address appear in the log...

Anywhere from your command line

git config —global user.name “my actualName”
git config —global user.email “m...@emailaddress.org”

Where those dashes before “global” above are two dashes. GitHub will otherwise 
associate your commits with your authentication

> 
> Regards,
> Gilles
> 
>> AuthorDate: Thu May 9 00:35:29 2019 +0530
>> 
>>Update pom.xml
>> ---
>> pom.xml | 3 +++
>> 1 file changed, 3 insertions(+)
>> 
>> diff --git a/pom.xml b/pom.xml
>> index cdac4f7..8d43d2a 100644
>> --- a/pom.xml
>> +++ b/pom.xml
>> @@ -74,6 +74,9 @@
>> 
>>   Artem Barger
>> 
>> + 
>> +  Abhishek Singh Dhadwal
>> +
>>   
>> 
>>   
>> 
> 
> -
> 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

Re: Using email addresses in exception messages

[Rob Tompkins]

> On May 12, 2019, at 6:45 AM, sebb  wrote:
> 
> Some of our code has Exception messages such as the following:
> 
>>> (Collections:LRUMap)
> throw new IllegalStateException("Entry.before is null." +
> " Please check that your keys are immutable, and that you have used
> synchronization properly." +
> " If so, then please report this to dev@commons.apache.org as a bug.");
> <<
> 
> I guess it seemed like a good idea at the time, but I think the idea
> has backfired:
> 
> https://lists.apache.org/thread.html/3363e23218b4c1c21b8093321ac293d68d2e4ab35b982adb53b1d5d6@%3Cdev.commons.apache.org%3E
> 
> I have seen about 30 of these mails altogether so far.
> 
> The intention was for the developer to capture the exception, check
> for the possible programming errors and then inform Commons developers
> if they believe there is a bug.
> 
> However it looks like the developers in the case have shown the error
> message direct to end users.
> 
> I think the messages (there are quite a lot in Collections, possibly
> elsewhere) should not include an email address. Instead maybe say
> something like:
> 
>>> 
> throw new IllegalStateException("Entry.before is null." +
> " This should not occur if your keys are immutable, and you have used
> synchronization properly." +
>>> 
> 
> This would leave it up to the developers to work out how contact us
> once they have eliminated any programming errors. Whilst this is a bit
> more work for the developers, I don't think it's unreasonable to
> expect developers to know how to report bugs in code they are using.
> 
> WDYT?

I would think that contact information in an error seems to be strange. I would 
prefer why the error happened as you suggested. 

Hopefully users of our libraries understand how to get in contact with us. But, 
given my experience at $work, that’s not always the case.

-Rob

> 
> -
> 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

Re: [GSoC] commons-gsoc Thursday meeting?

[Rob Tompkins]

On 5/14/2019 12:47 PM, Eric Barnhill wrote:

Should we have another Slack meeting at the same time this Thursday, 5pm
UTC (9am California time)?



+1



The first focus of this meeting will be blockers and other questions the
mentees have, trying to get up to speed on command line git, maven and
POMs, and IDEs. Everyone should bring at least one thing to ask about. We
will otherwise assume the mentees are ready to go with these topics.

After that we'll move on to goals for the next week. I propose this goal is
a software flowchart of your commons component that you will be developing.
This can be in as much detail as you like, including method names, doc,
etc. The more you mock out, the easier your later work will be, and mine
too.

In particular, you have probably noticed that maven creates src/main and
src/test folders. Even if you have already done some flowcharting for your
component, see if you can start to flowchart the unit tests. As I said on
the Slack you may even find it interesting to sketch the tests first as it
will give your coding work a clear endpoint to focus on. Don't
underestimate how much time testing and doc will take you -- it can take
half of your time with new projects.

This is all flexible but we will need to see a detailed spec to sign off on
clearing the project out of community bonding.

So, I'll be available to answer questions on that next step as well.



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [IO] Update to Java 8

[Rob Tompkins]

On 5/15/2019 2:42 PM, Gary Gregory wrote:

Hi all,

Time to update to Java 8 methinks.


+1



Gary



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [gsoc][statistics] Enable Travis

[Rob Tompkins]

> On May 18, 2019, at 6:30 AM, Gilles Sadowski  wrote:
> 
> Hi.
> 
>>> 
 On 17 May 2019, at 23:24, Gilles Sadowski >>> > wrote:
 
 Hi.
 
> Le ven. 17 mai 2019 à 18:33, Alex Herbert  > a écrit :
> 
> There is no .travis.yml file for Statistics and so PRs from GSoC mentees
> are without checks.
> 
> Plus I do not know how to check if the Travis integration is active for
> this project.
 
 I filed a request at INFRA:
 https://issues.apache.org/jira/browse/INFRA-18398 
 
>>> 
>>> OK. I didn’t know that was how it worked.
>>> 
>>> I’ve pushed to my PR and Travis is working.
>> 
>> Oh, no coverage info. Does coveralls require INFRA as well?
>> 
> 
> Seems so.  I filed:
>  https://issues.apache.org/jira/browse/INFRA-18399

I’ll sort out the Travis code tonight or tomorrow night. -Rob

> 
> Gilles
> 
> -
> 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

Re: [commons-statistics] branch master updated: Added pmd plugin configuration to build.

[Rob Tompkins]

> On May 20, 2019, at 6:58 AM, aherb...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> aherbert pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/commons-statistics.git
> 
> 
> The following commit(s) were added to refs/heads/master by this push:
> new f929f96  Added pmd plugin configuration to build.
> f929f96 is described below
> 
> commit f929f96fe0399c08e7a545cfe9bea2ceb0fab69f
> Author: aherbert 
> AuthorDate: Mon May 20 11:58:45 2019 +0100
> 
>Added pmd plugin configuration to build.
> ---
> pom.xml | 58 ++
> 1 file changed, 38 insertions(+), 20 deletions(-)
> 
> diff --git a/pom.xml b/pom.xml
> index e8335d9..842ea30 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -176,7 +176,7 @@
>   
> 
>   
> -clean verify apache-rat:check clirr:check checkstyle:check 
> spotbugs:check javadoc:javadoc
> +clean verify apache-rat:check clirr:check checkstyle:check 
> pmd:check spotbugs:check javadoc:javadoc

thanks for that catch.

> 
>   
> org.apache.maven.plugins
> @@ -228,6 +228,12 @@
>   
> org.apache.maven.plugins
> maven-checkstyle-plugin
> +
> +  
> ${statistics.parent.dir}/src/main/resources/checkstyle/checkstyle.xml
> +  
> ${statistics.parent.dir}/src/main/resources/checkstyle/license-header.txt
> +  false
> +  false
> +
> 
>   
> validate
> @@ -239,6 +245,18 @@
> 
>   
>   
> +maven-pmd-plugin
> +${statistics.pmd.version}
> +
> +  ${maven.compiler.target}
> +  false
> +  true
> +  
> +
> ${statistics.parent.dir}/src/main/resources/pmd/pmd-ruleset.xml
> +  
> +
> +  
> +  
> com.github.spotbugs
> spotbugs-maven-plugin
> ${statistics.spotbugs.version}
> @@ -344,16 +362,6 @@
> 
>   
>   
> -com.github.spotbugs
> -spotbugs-maven-plugin
> -${statistics.spotbugs.version}
> -
> -  Normal
> -  Default
> -  
> ${statistics.parent.dir}/src/main/resources/spotbugs/spotbugs-exclude-filter.xml
> -
> -  
> -  
> org.apache.maven.plugins
> maven-checkstyle-plugin
> ${statistics.checkstyle.version}
> @@ -372,15 +380,6 @@
> 
>   
>   
> -org.codehaus.mojo
> -clirr-maven-plugin
> -${statistics.clirr.version}
> -
> -  ${minSeverity}
> -  
> ${statistics.parent.dir}/src/main/resources/clirr/clirr-ignored.xml
> -
> -  
> -  
> maven-pmd-plugin
> ${statistics.pmd.version}
> 
> @@ -399,6 +398,25 @@
>   
> 
>   
> +  
> +com.github.spotbugs
> +spotbugs-maven-plugin
> +${statistics.spotbugs.version}
> +
> +  Normal
> +  Default
> +  
> ${statistics.parent.dir}/src/main/resources/spotbugs/spotbugs-exclude-filter.xml
> +
> +  
> +  
> +org.codehaus.mojo
> +clirr-maven-plugin
> +${statistics.clirr.version}
> +
> +  ${minSeverity}
> +  
> ${statistics.parent.dir}/src/main/resources/clirr/clirr-ignored.xml
> +
> +  
>   
>   
> org.apache.maven.plugins
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [GSoC] Thursday mentee meeting

[Rob Tompkins]

I can be there.

> On May 22, 2019, at 5:32 PM, Ben Nguyen  wrote:
> 
> Hello,
> 
> I have a dentist appointment around that time (starting -30 mins from meeting 
> time), but will try to text during my bus commutes.
> I will try to post my updated flow charts and a starting unit tests 
> check-list before the meeting in the ML/Slack.
> 
> Cheers,
> -Ben
> 
> From: Abhishek Dhadwal
> Sent: Wednesday, May 22, 2019 2:34 PM
> To: Commons Developers List
> Subject: Re: [GSoC] Thursday mentee meeting
> 
> Hi,
> Unfortunately, I won't be able to attend the meeting due to a wedding.
> Regards,
> Abhishek
> 
>> On Thu, May 23, 2019, 00:21 Eric Barnhill  wrote:
>> 
>> Let's have another mentee meeting Thursday morning, same time as the
>> previous two. (Sorry about the miscommunication Abhishek).
>> 
>> As preparation for this meeting please have prepared a detailed flow
>> diagram for your proposed components, ideally with sufficient detail that
>> it includes some unit tests. The more you mark up in advance the easier
>> coding will be when it starts next week.
>> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org