I agree with this statement generally. That said, this doesn’t surprise me that
I made this error because japicmp is minimally cumbersome to work with. It
feels very unfinished/unpolished. Next time I get into [parent], I’ll try to go
up and submit more polishing work to the japicmp codebase.
> On Aug 12, 2018, at 11:16 AM, Stefan Bodewig wrote:
>
>> On 2018-08-12, Rob Tompkins wrote:
>>
>> I agree with this statement generally. That said, this doesn’t
>> surprise me that I made this error because japicmp is minimally
>> cumbersome to work w
Hello all,
I’m planning on working on 3.8 for lang later this week. Does anyone want to
get any specific jira's in? I think that I can quickly button up LANG-1408
(selfishly want to get that in).
Cheers,
-Rob
-
To unsubscribe,
+1
'mvn clean test package site' works with
$ mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T14:33:14-04:00)
Maven home: /usr/local/Cellar/maven/3.5.4/libexec
Java version: 1.8.0_172, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jd
> On Aug 14, 2018, at 12:26 AM, Stefan Bodewig wrote:
>
>> On 2018-08-14, Rob Tompkins wrote:
>>
>> Must fix during artifact promotion:
>
>> (1) Signature files contain more than the correct signatures (note the
>> contents below):
>
>
Here’s my +1 for this RC.
-Rob
> On Aug 10, 2018, at 9:52 PM, Rob Tompkins wrote:
>
> We have added some significant enhancements since Apache Commons RNG 1.0 was
> released, so I would like to release Apache Commons RNG 1.1.
>
> Apache Commons RNG 1.1 RC7 is availab
This vote passes with +1’s from the following (in order of appearance):
Gilles,
Gary Gregory, and
Rob Tompkins.
Many thanks for all of the patience with me on this RC, as it is the first
multi module component to consume the release-plugin. I will perform the
promotions over the next day or so
It looks like RNG’s Jira space has a different permission profile than [LANG]
in which I could create a new version if I wanted. Does anyone know what might
be going on here?
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@common
@Sebb with this new version of Jira, I couldn’t find your checkbox to not send
email notifications on the bulk transition. Do you know if it still exists?
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For addi
> On Aug 14, 2018, at 10:07 AM, sebb wrote:
>
> No idea, please ask Infra
Sounds good.
-Rob
>
> On 14 August 2018 at 14:50, Rob Tompkins wrote:
>> @Sebb with this new version of Jira, I couldn’t find your checkbox to not
>> send email notifications on the bulk
q-p/703182>
Thoughts?
Cheers,
-Rob
> On Aug 14, 2018, at 10:13 AM, Rob Tompkins wrote:
>
>
>
>> On Aug 14, 2018, at 10:07 AM, sebb wrote:
>>
>> No idea, please ask Infra
>
> Sounds good.
>
> -Rob
>>
>> On 14 August 2018 at 14:50, Rob
> On Aug 14, 2018, at 11:04 AM, Gilles wrote:
>
> On Tue, 14 Aug 2018 09:43:45 -0400, Rob Tompkins wrote:
>> It looks like RNG’s Jira space has a different permission profile
>> than [LANG] in which I could create a new version if I wanted. Does
>> anyone know
'd take too long to
> fix it. WDYT?
>
With the new plugin rolling releases is at least a little easier, so if you
want to do 3.9 in a month even, I’d be happy to.
-Rob
> Cheers
> Bruno
>
>
> https://issues.apache.org/jira/browse/LANG-1339
>
> https://githu
/userguide/index.html
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
Not a problem. Will try to cut the 3.8 [lang] RC1 tonight.
> On Aug 15, 2018, at 10:08 AM, Gary Gregory wrote:
>
> Thank you Rob for your diligence and patience RM'ing this release through
> so many RCs! :-)
>
> Gary
>
> On Wed, Aug 15, 2018 at 7:06 AM Rob Tomp
I’ll look into this after I finish up with the [lang] RC.
> On Aug 15, 2018, at 6:41 PM, Gilles wrote:
>
> Hi.
>
> Build on "master" fails after the batch of commits post-release.
> See console output excerpt below.
>
> ---CUT---
> [INFO] Generating "JDepend" report ---
> jdepend
Pardon, I didn’t include RELEASE-NOTES-3.8.txt in the site in that tag.
> On Aug 15, 2018, at 9:31 PM, chtom...@apache.org wrote:
>
> Repository: commons-lang
> Updated Tags: refs/tags/LANG_3_8_RC1 [deleted] 7cd151ee6
-
To uns
[ ] -1 I oppose this release because...
Thank you,
Rob Tompkins,
Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
ge it upon
promotion.
-Rob
> Gary
>
>
>> +1
>>
>> Oliver
>>
>>> Am 16.08.2018 um 03:54 schrieb Rob Tompkins:
>>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Lang 3.7 was
Will try to get there through the weekend.
-Rob
> On Aug 16, 2018, at 11:42 AM, Gary Gregory wrote:
>
> If anyone feels like RM'ing, we need a new [release-plugin] following by
> using that in a new [commons-parent].
>
> Gary
--
> On Aug 15, 2018, at 6:41 PM, Gilles wrote:
>
> Hi.
>
> Build on "master" fails after the batch of commits post-release.
> See console output excerpt below.
>
This is indeed weird. I’ve seen a bunch of things that cite aspect weaving as
the root cause of the issue (specifically it’s us [b
> On Aug 18, 2018, at 10:40 AM, Gilles wrote:
>
>> On Sat, 18 Aug 2018 08:23:55 -0600, Gary Gregory wrote:
>> Right now our release plugin snapshot creates both SHA256 and SHA512 files.
>> I wonder if we should simply only generate SHA512.
>
> The download page only shows sha256:
> http://co
Here’s my +1.
> On Aug 15, 2018, at 9:54 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Lang 3.7 was released, so I would like to release Apache
> Commons Lang 3.8.
>
> Apache Commons Lang 3.8
This [VOTE] passes with the following votes (in order of appearance):
Bruno Kinoshita: +1,
Gary Gregory: +1,
Oliver Heger: +1,
Benedikt Ritter: +1, and
Rob Tompkins: +1
I will go through the release promotion in the next 24 hours. Many thanks to
the validators for their eyes and work.
-Rob
commons-lang3
3.8
Best regards,
Rob Tompkins
on behalf of the Apache Commons community
dea, please ask Infra
>>
>> On 14 August 2018 at 14:50, Rob Tompkins wrote:
>>> @Sebb with this new version of Jira, I couldn’t find your checkbox to not
>>> send email notifications on the bulk transition. Do you know if it still
>>> exists?
>>>
&g
I’m curious to gauge what people think here. My general thought is no breaking
BC without a major version change. So, even though this is an internal
component, we stick with the rules because we never know who else might be
using the component, right?
-Rob
-
> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>
> Hi,
>
> I don't understand this discussion. Changes in Commons Parent have broken
> the commons-compress build. So we should either roll this changes back or
> those who need the changes in commons parent should fix the commons
> compre
> On Aug 22, 2018, at 8:32 AM, Gilles wrote:
>
> On Wed, 22 Aug 2018 08:11:03 -0400, Rob Tompkins wrote:
>>> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>>>
>>> Hi,
>>>
>>> I don't understand this discussion. Changes in Co
Seems reasonable. Should we go with 2.0?
-Rob
> On Aug 22, 2018, at 6:35 AM, Gilles wrote:
>
> On Tue, 21 Aug 2018 22:04:12 -0400, Rob Tompkins wrote:
>> I’m curious to gauge what people think here. My general thought is no
>> breaking BC without a major version change. So
ng the component even though our
intent is for only us to use it.
-Rob
>
> Gary
>
> On Wed, Aug 22, 2018 at 7:04 AM Rob Tompkins wrote:
>
>> Seems reasonable. Should we go with 2.0?
>>
>> -Rob
>>
>>> On Aug 22, 2018, at 6:35 AM, Gilles
>
> On Aug 22, 2018, at 9:03 AM, Stefan Bodewig wrote:
>
> On 2018-08-22, Rob Tompkins wrote:
>
>>> On Aug 22, 2018, at 1:47 AM, Benedikt Ritter wrote:
>
>>> Hi,
>
>>> I don't understand this discussion. Changes in Commons Parent have b
Just didn’t want to duplicate effort if someone else was planning to work on it.
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
lease 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)
-
To unsubscri
> On Aug 27, 2018, at 2:33 PM, Pascal Schumacher
> wrote:
>
> At least RAT and clirr/japicmp should be part of default goal.
>
> I'm personally prefer checkstyle and findbugs/spotbugs (although I prefer
> error-prone nowadays) to be part of the default goal.
>
> On Java 8+ it is also helpf
Here’s my +1.
> On Aug 24, 2018, at 9:56 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Release Plugin 1.3 was released, so I would like to release
> Apache Commons Release Plugin 1.4.
>
> A
This [LAZY][VOTE] passes with +1’s from Gary as well as myself. I will perform
the release processing.
Cheers,
-Rob
> On Aug 24, 2018, at 9:56 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Release Pl
[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.4.
The Apache Commons Release Plugin is a collection of Java based Maven mojos for
Apache Commons
Release process. These mojos are intend
> On Aug 29, 2018, at 4:43 PM, Matt Benson wrote:
>
> I have opened and resolved [1]. I classified this as a bug. Should we
> consider a 1.4.1 release or just leave the master version at 1.5-SNAPSHOT?
I can do either. Seems like a good move before [parent] v48. Thoughts?
-Rob
> It appears I
> On Aug 29, 2018, at 7:16 PM, Matt Benson wrote:
>
>> On Wed, Aug 29, 2018, 5:41 PM Rob Tompkins wrote:
>>
>>
>>
>>> On Aug 29, 2018, at 4:43 PM, Matt Benson wrote:
>>>
>>> I have opened and resolved [1]. I classified this as a
> On Aug 31, 2018, at 4:46 AM, Benedikt Ritter wrote:
>
> Am Do., 30. Aug. 2018 um 13:45 Uhr schrieb sebb :
>
>> On 30 August 2018 at 11:19, Thomas Vandahl wrote:
>>> On 28.08.18 12:03, sebb wrote:
On 28 August 2018 at 09:25, Mark Struberg
>> wrote:
>> This is unlikely to happen as
> On Sep 19, 2018, at 4:25 AM, Benedikt Ritter wrote:
>
> ... bringing this to the developers list...
>
> I think this issue has been caused by this change:
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=1833874&r2=1833926
Do we roll a 3.8.1?
-Rob
>
> I don't
My impression was that we had this conversation, and we decided that we wanted
this the other way around and to fix the components respectively due to the
semantics of the issue at hand based on what Gary said below.
-Rob
> On Sep 19, 2018, at 8:45 AM, Gary Gregory wrote:
>
> The difference
> On Sep 19, 2018, at 9:28 AM, Gilles wrote:
>
>> On Wed, 19 Sep 2018 06:45:13 -0600, Gary Gregory wrote:
>> The difference is to account for artifact ids that contain a version like
>> commons-lang3. The component id is then just commons-lang. You must not
>> have versions in names for certai
I think the plan moving forward here is that we should do the following:
math
math4
And change [parent] back to
https://svn.apache.org/repos/infra/websites/production/commons/content/proper/${commons.componentid}
Yeah?
-Rob
> On Sep 19, 2018, at 9:36 AM, Rob Tompkins wrote:
>
>
Do we have a JIRA for this?
> On Sep 19, 2018, at 7:59 AM, Benedikt Ritter wrote:
>
> Hi,
>
> Am Mi., 19. Sep. 2018 um 13:44 Uhr schrieb Rob Tompkins <mailto:chtom...@gmail.com>
>> :
>
>>
>>
>>> On Sep 19, 2018, at 4:25 AM, Be
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Rob Tompkins,
Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314)
-
To unsubscribe, e-mail: dev-unsubscr...@co
e: C:\Program
>> Files\Java\jdk1.8.0_181\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> Reports LGTM.
>>
>> Gary
>> Gary
viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=1831599&r2=1832339
>
> Am Mi., 19. Sep. 2018 um 17:25 Uhr schrieb Gary Gregory <
> garydgreg...@gmail.com>:
>
>> On Wed, Sep 19, 2018 at 8:30 AM Rob Tompkins wrote:
>>
>>> I think
> On Sep 20, 2018, at 9:31 AM, Gilles wrote:
>
> On Thu, 20 Sep 2018 08:53:38 -0400, Rob Tompkins wrote:
>>> On Sep 20, 2018, at 3:10 AM, Benedikt Ritter wrote:
>>>
>>> Hello,
>>>
>>> Reverting this change was discussed here [1]. It
> On Sep 21, 2018, at 11:26 AM, Gary Gregory wrote:
>
> On Fri, Sep 21, 2018 at 7:05 AM Gilles <mailto:gil...@harfang.homelinux.org>> wrote:
>
>> On Fri, 21 Sep 2018 08:52:37 -0400, Rob Tompkins wrote:
>>>> On Sep 20, 2018, at 9:31 AM, Gilles
>>&
Here’s my +1.
-Rob
> On Sep 19, 2018, at 12:04 PM, Rob Tompkins wrote:
>
> We have fixed LANG-1419 "Restore BundleSymbolicName / regression in version
> 3.8.0", so I would like to release Apache Commons Lang 3.8.1.
>
> Apache Commons Lang 3.8.1 RC1 is available
This vote passes with the following votes:
Gary Gregory: +1,
Oliver Heger: +1, and
Rob Tompkins: +1.
I will perform the release now and will announce the release tomorrow. Many
thanks to all of those that helped on this one.
-Rob
> On Sep 19, 2018, at 12:04 PM, Rob Tompkins wrote:
>
ndor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_181\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Reports LGTM.
>
> Gary
> Ga
dist/commons <http://www.apache.org/dist/commons>
Maven artifacts are also available in the central Maven repository:
org.apache.commons
commons-lang3
3.8.1
Best regards,
Rob Tompkins
on behalf of the Apache Commons community
e 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 (
only real worrisome one IMO is:
> "org.apache.commons.text.lookup.PropertiesStringLookup.lookup(String)
> may fail to close stream"
>
> If we fix one, we might as well fix them all.
>
> WDYT?
>
I’m ok with the work for a rebuild.
-Rob
> Gary
>
>> On Fri, Sep 28, 2018 at 12:37 PM Rob Tompkins
> On Sep 29, 2018, at 8:42 PM, Gary Gregory wrote:
>
>> On Sat, Sep 29, 2018 at 6:24 AM Rob Tompkins wrote:
>>
>>
>>
>>> On Sep 28, 2018, at 9:36 PM, Gary Gregory
>> wrote:
>>>
>>> Hi,
>>>
>>> It looks
I am cancelling this vote to pull in some spot bugs errors.
-Rob
> On Sep 28, 2018, at 2:37 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Text 1.4 was released, so I would like to release Apache
> C
/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 (
the missing file and the
> build went all the way through.
>
> From the src zip:
>
> ASC, SHA256, SHA512 OK.
>
> Odd:
> https://dist.apache.org/repos/dist/dev/commons/text/1.5-RC1/site/rat-report.html
> is not found
>
> Gary
>
>> On Sat, Sep 29, 2018
This vote is cancelled. I’ll rebuild soon.
> On Sep 29, 2018, at 11:02 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Text 1.4 was released, so I would like to release Apache
> Commons Text 1.5.
>
/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 (
Here’s my +1.
-Rob
> On Oct 1, 2018, at 9:03 AM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Text 1.4 was released, so I would like to release Apache
> Commons Text 1.5.
>
> Apache Commons Text
This vote passes with the following votes (in order of appearance):
Gary Gregory: +1,
Pascal Schumacher: +1,
Eltan Alder: +1 (non-binding),
Amey Jade: +1 (non-binding),
Bruno Kinoshita: +1,
Rob Tompkins: +1.
Many thanks to all of those that validated this release candidate. I will now
perform
t, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the Apache
Commons Text website:
http://commons.apache.org/proper/commons-text/
<http://commons.apache.org/proper/commons-text/>
Best regards,
Rob Tompkins
on behalf of the Apache Commons community
ww.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
Here’s my +1 on the [VOTE].
-Rob
> On Oct 12, 2018, at 10:01 PM, Rob Tompkins wrote:
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Text 1.5 was released, so I would like to release Apache
> Commons Text 1.6.
>
> Apache
This [VOTE] passes with the following votes in order of appearance:
Gary Gregory: +1,
Pascal Schumacher: +1, and
Rob Tompkins: +1.
Many thanks for all of the effort that went into this release. I will perform
the release processes now, and I’ll send out the announcement tomorrow.
Cheers,
-Rob
://commons.apache.org/proper/commons-text/
Best regards,
Rob Tompkins
on behalf of the Apache Commons community
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...
Tha
trunk.
>
> Post release, I think this sentence can be removed from the release
> notes: "Tools
> to assist in the reading of configuration/preferences files in various
> formats".
>
> Gary
>
>
>> On Tue, Oct 23, 2018 at 1:22 PM Rob Tompkins wrote:
&
I’m cancelling this vote because of the rat report failure and my -1.
-Rob
> From: Rob Tompkins
> Date: October 23, 2018 at 3:21:56 PM EDT
> To: Commons Developers List
> Subject: [VOTE] Release Apache Commons Configuration 2.4 based on RC1
>
> We have fixed quite a few b
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
legalArgumentException: Unsupported class file major version 55
>>at
>> org.apache.commons.configuration2.reloading.TestFileHandlerReloadingDetector.testRefreshIsReloadingRequiredTrue(TestFileHandlerReloadingDetector.java:131)
>>
>> [ERROR]
>> testIsReloadingRequiredTrue(org.apache.com
I’ll throw in my +1 just to keep the ball rolling. But it was the trivial +1.
-Rob
> On Oct 26, 2018, at 10:12 PM, Gary Gregory wrote:
>
> A reminder that we need more votes ;-)
>
> Gary
>
>> On Tue, Oct 23, 2018 at 8:10 PM Rob Tompkins wrote:
>>
>>
This is mildly on me for not updating the release docs recently. I’ll put that
on my docket for the week.
PS. @Bruno solid work and many thanks for rolling the RC.
Cheers,
-Rob
> On Oct 28, 2018, at 9:35 AM, Gary Gregory wrote:
>
> Hello Bruno,
>
> Thank you for preparing the RC.
>
> MD5 a
imaging RC2.
I’ll try to work on this this morning (UTC-4) both on the [site] as well as
sending the details over to you.
-Rob
>
>
>
> Thanks heaps
> Bruno
>
>
>
>
>
> From: Rob Tompkins
> To: Commons Developers List
&
This [VOTE] thread passes with votes from (in order of appearance):
Gary Gregory: +1,
Rob Tompkins: +1, and
Bruno Kinoshita: +1.
I will perform the release activities now and will send the release
announcement tomorrow.
Many thanks for the validations,
-Rob
> On Oct 23, 2018, at 10:10
> On Oct 29, 2018, at 7:24 AM, Rob Tompkins wrote:
>
>
>
>> On Oct 28, 2018, at 8:04 PM, Bruno P. Kinoshita wrote:
>>
>> Will cancel the vote tonight, thanks for spotting that @Gary.
>>
>> @Rob, thanks a lot for all the great work on the new pl
submit bug reports, patches, or suggestions for improvement, see the Apache
Commons Configuration website:
http://commons.apache.org/proper/commons-configuration/
Best regards,
Rob Tompkins
on behalf of the Apache Commons community
I can’t see why not to do this.
+1 to the idea
> On Nov 4, 2018, at 7:08 AM, Otto Fowler wrote:
>
> +1
>
>
> On November 3, 2018 at 10:55:08, Gary Gregory (garydgreg...@gmail.com)
> wrote:
>
> I propose we update the Java requirement for [vfs] from Java 7 to Java 8.
>
> Gary
-
Curious to see what people’s thoughts are to this:
https://aws.amazon.com/corretto/
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Pardon my being a little late to the party here.
Thoughts in going through release validation (might be a tad redundant):
- We’re not much used to the maven assemblies being deployed to nexus,
but that isn’t necessarily a problem.
- Why do we have a "-source-release” and a “-src”
I’d be happy to roll the release if we get master to where you want it.
Cheers,
-Rob
> On Nov 19, 2018, at 7:18 AM, Mark Struberg wrote:
>
> Oki, I now see what you mean.
>
> We actually have 3 source zips now.
>
> .src.zip
> .source-release.zip
> src.jar
>
> That's a mess.
>
> There shoul
> On Nov 19, 2018, at 5:27 PM, Gary Gregory wrote:
>
> HI all:
>
> When I run 'mvn clean verify' on git master, I get test failures on my
> rather busy CPU (~60-90%):
>
> [INFO] Running org.apache.commons.pool2.impl.TestGenericKeyedObjectPool
> [ERROR] Tests run: 63, Failures: 2, Errors: 0,
> On Nov 22, 2018, at 11:49 AM, Gary Gregory wrote:
>
> On Fri, Nov 16, 2018 at 2:55 PM Gary Gregory wrote:
>
>> Should we cancel this RC to include:
>>
>> https://issues.apache.org/jira/browse/POOL-359
>>
>
> This is now in git master.
>
> Feel free to roll RC3.
Who’s on for this one?
Yeah. I can try to start pulling that together between now and tomorrow sort of
time frame.
> On Nov 22, 2018, at 1:11 PM, Gary Gregory wrote:
>
>> On Thu, Nov 22, 2018 at 10:08 AM Rob Tompkins wrote:
>>
>>
>>
>>> On Nov 22, 2018, at 11:49 AM, Gary
> On Nov 22, 2018, at 3:26 PM, Gary Gregory wrote:
>
>> On Thu, Nov 22, 2018, 12:55 Rob Tompkins >
>> Yeah. I can try to start pulling that together between now and tomorrow
>> sort of time frame.
>
>
> Enjoy the turkey!
>
Thanks. You too.
>
> On Nov 22, 2018, at 1:11 PM, Gary Gregory wrote:
>
> On Thu, Nov 22, 2018 at 10:08 AM Rob Tompkins <mailto:chtom...@gmail.com>> wrote:
>
>>
>>
>>> On Nov 22, 2018, at 11:49 AM, Gary Gregory
>> wrote:
>>>
>>> On Fri, N
> On Nov 23, 2018, at 10:51 AM, Phil Steitz wrote:
>
> On 11/23/18 2:57 AM, Mark Struberg wrote:
>> should read: This change (putting a new item back to the idle pool) was
>> needed to prevent a dead-lock
>>
>> *grabbing a fresh coffee* le
>
> I am sorry I did not look carefully enough
> On Nov 26, 2018, at 8:16 AM, Mark Struberg wrote:
>
> Hi Gary!
>
> I've added multi-line comments in the middle of code blocks I touched.
> e.g.
> https://github.com/apache/commons-pool/blob/016a1f67263fe1cde1d910dc7002d972811951c5/src/main/java/org/apache/commons/pool2/impl/GenericObjectP
I’ve been tasked with taking something to production at my day job using the
newest internal processes with a deadline of EOY. And, there’s just a lot to do
for that. So I’ve been fairly heavily distracted in that zone.
Just trying to keep everyone in the loop.
-Rob
I’ll try to get to validation on this by the end of the day, unless @Gilles,
you want to take into account the vote below.
-Rob
> On Dec 4, 2018, at 9:08 AM, Alex Herbert wrote:
>
> +0 (non-binding)
>
>
> The user guide shows updated Performance and Quality tables following the
> changes to
> On Dec 4, 2018, at 10:15 AM, Gilles wrote:
>
> On Tue, 4 Dec 2018 14:08:59 +, Alex Herbert wrote:
>> +0 (non-binding)
>>
>>
>> The user guide shows updated Performance and Quality tables following
>> the changes to the core implementation for all tables (verses release
>> 1.1). I note t
With:
$ mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T14:33:14-04:00)
Maven home: /usr/local/Cellar/maven/3.5.4/libexec
Java version: 9.0.4, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk-9.0.4.jdk/Contents/Home
Default locale:
> On Dec 6, 2018, at 6:37 AM, sebb wrote:
>
>> On Thu, 6 Dec 2018 at 10:58, Gilles wrote:
>>
>>> On Wed, 5 Dec 2018 21:29:26 -0500, Rob Tompkins wrote:
>>> With:
>>>
>>> $ mvn -version
>>> Apache Maven 3.5.4 (1edded09
Seems like we should put together an inventory, and pull the divide and conquer
strategy?? Who’s willing to lend hands here?
-Rob
> On Dec 8, 2018, at 8:38 AM, Gary Gregory wrote:
>
> Sounds good.
>
> Gary
>
> On Fri, Dec 7, 2018, 17:33 Gilles
>> Hi.
>>
>> [See message quoted below.]
>>
+1 (I predicate this on our being ok with a java 9 build only)
clirr - good (2 info issues)
rat - good
pmd - few nits
checkstyle - good
signatures - good
build java9 only:
$ mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T14:33:14-04:00)
Maven home: /usr/loc
Infra stated that we need documented consensus on this. So, let’s have at it.
I propose that we move the following repos over to gitbox:
commons-build-plugin.git 11 weeks ago
commons-cli.git30 weeks ago
commons-collections.git15 days ago
commons-compress.git 19 days ago
c
901 - 1000 of 1475 matches
Mail list logo
