Re: [VOTE] Redirect github notifications to issues@

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

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

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

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

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

Re: Google Summer of Code 2019 Mentor Registration

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

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

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

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

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: > > @aherbe

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

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, &g

Re: [Parent] RAT check

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

[all] GitHub Release Notes

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

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

/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

Re: [release][build] Merge plugins?

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

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

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

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

5bb9d6ebd7a1b52 > > 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 a

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

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

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

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

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

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

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

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

[GSoC] Example Issues From 2018 or upcoming 2019

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.

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

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

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.

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

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 enhanceme

Re: [ANNOUNCE] Commons Release Plugin 1.6 released.

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

[ANNOUNCE] Apache Commons Build Plugin 1.10 Released

[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

Re: [all] GitHub Release Notes

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

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

ifacts [ ] +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 candidat

[all] What versions of java do we support?

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

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

+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

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

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

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

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

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

Re: [codec] Java 8

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

Re: [codec] Java 8

rity 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. >> >&g

Re: [LANG] Jenkins Pipeline DSL

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 le

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

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

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

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 1

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

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 Com

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

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

Re: [codec] RAT check in Jenkins vs local

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

[ANNOUNCE] Commons Parent 48 released.

[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: CO

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

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

[lang] Towards 3.9

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

Re: [lang] Towards 3.9

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

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

> 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

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

2: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 mat

Re: [lang] Towards 3.9

> 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

Re: [lang] Towards 3.9

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

Re: [lang] Towards 3.9

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

[lang] LANG-1442

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

> 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

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

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

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

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

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

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

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

> 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

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

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

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

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

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

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

[lang] 3.9, switch from cobertura to jacoco?

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,

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

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

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

> 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

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

> 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

[VOTE] Release Apache Commons Lang 3.9 based on RC1

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

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

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

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

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

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

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

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

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

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

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.

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

> 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

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

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

Re: [BCEL] Console warning

> 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

Re: [BCEL] Console warning

> 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

[VOTE] Release Apache Commons Lang 3.9 based on RC2

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

Re: Link from github to gitbox broken

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 no

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

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

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

> 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

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

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 La

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

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

Re: Nexus: Promotion Completed

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

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

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

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

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

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

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 releas

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

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

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

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

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

+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

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

n. >>>>>>> remote: >>>>>>> To https://gitbox.apache.org/repos/asf/commons-vfs >>>>>>> ! [remote rejected] trunk (pre-receive hook declined) >>>>>>> error: failed to push some refs to ' >>>>>&

Re: [daemon] release 1.1.1?

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

Re: [daemon] release 1.1.1?

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

Re: [bcel] broken repo?

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

Re: [bcel] broken repo?

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

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

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

Re: [bcel] broken repo?

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

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

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

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

> 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

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

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

Re: Using email addresses in exception messages

> 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

Re: [GSoC] commons-gsoc Thursday meeting?

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 an

Re: [IO] Update to Java 8

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

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

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

> 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

Re: [GSoC] Thursday mentee meeting

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

  1   2   3   4   5   6   7   8   9   10   >