Re: [math][statistics] StatUtils

Me neither. But, on the other hand, is not StringUtils the most used class across all the Commons components? Just to understand how people will actually make use of the new library. On Jan 5, 2018 02:35, "Gary Gregory" wrote: I am not a fan of call classes SomethingUtils, it feels like a cop ou

Re: [VOTE] Create new component commons-release-plugin

+1 On Jan 4, 2018 17:56, "Rob Tompkins" wrote: > Hello all, > > I propose that we create a new component [commons-release-plugin] to be > managed in the same fashion as the commons-build-plugin, and by that I mean: > > * Use COMMONSSITE as the jira area > * Create a git repo > * Include it in th

Re: [math][statistics] StatUtils

I am not a fan of call classes SomethingUtils, it feels like a cop out. Gary On Jan 4, 2018 5:55 PM, "Gilles" wrote: > On Thu, 4 Jan 2018 17:25:17 -0700, Gary Gregory wrote: > >> Hi All, >> >> I'm not sure where we are WRT [math] spawning [statistics] but it would be >> nice if the StatUtils cl

Re: [math][statistics] StatUtils

On Thu, 4 Jan 2018 17:25:17 -0700, Gary Gregory wrote: Hi All, I'm not sure where we are WRT [math] spawning [statistics] but it would be nice if the StatUtils classs would work with Objects like java.time.Duration, as in StatUtils.mean(Duration[]) Waiting for JIRA to be set up: https://i

[math][statistics] StatUtils

Hi All, I'm not sure where we are WRT [math] spawning [statistics] but it would be nice if the StatUtils classs would work with Objects like java.time.Duration, as in StatUtils.mean(Duration[]) Gary

Re: [VOTE] Create new component commons-release-plugin

+1 Am 04.01.2018 um 17:56 schrieb Rob Tompkins: Hello all, I propose that we create a new component [commons-release-plugin] to be managed in the same fashion as the commons-build-plugin, and by that I mean: * Use COMMONSSITE as the jira area * Create a git repo * Include it in the same porti

Re: [VOTE] Create new component commons-release-plugin

+1 Great work, Rob! Many thanks! Oliver Am 04.01.2018 um 17:56 schrieb Rob Tompkins: > Hello all, > > I propose that we create a new component [commons-release-plugin] to be > managed in the same fashion as the commons-build-plugin, and by that I mean: > > * Use COMMONSSITE as the jira area >

Re: [VOTE] Create new component commons-release-plugin

On Thu, 4 Jan 2018 11:56:40 -0500, Rob Tompkins wrote: Hello all, I propose that we create a new component [commons-release-plugin] to be managed in the same fashion as the commons-build-plugin, and by that I mean: * Use COMMONSSITE as the jira area * Create a git repo * Include it in the same

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

> On Jan 4, 2018, at 1:36 PM, Gary Gregory wrote: > > It seems that in this case, we are creating a new internal component, no > sandbox. Like commons-parent and the build plugin. Agreed, but I would think the process for component creation would be analogous to that of moving a component out

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

It seems that in this case, we are creating a new internal component, no sandbox. Like commons-parent and the build plugin. Gary On Thu, Jan 4, 2018 at 11:19 AM, Rob Tompkins wrote: > I didn’t read back over the moving a component out of the sandbox bit, so > I figured I’d just go with the form

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

I didn’t read back over the moving a component out of the sandbox bit, so I figured I’d just go with the formality. > On Jan 4, 2018, at 12:33 PM, Gary Gregory wrote: > > Hi Rob, > > I do not think we need a formal VOTE until we want to release, but why not. > Reusing COMMONSITE makes sense f

Re: [VOTE] Create new component commons-release-plugin

[ X ] +1 Create the component Thanks for working on this! Bruno From: Rob Tompkins To: Commons Developers List Sent: Friday, 5 January 2018 5:56 AM Subject: [VOTE] Create new component commons-release-plugin Hello all, I propose that we create a new

Re: commons-compress git commit: Update XZ for Java dependency

Great news. Thank you for the update. Gary On Thu, Jan 4, 2018 at 10:58 AM, Stefan Bodewig wrote: > On 2018-01-04, Gary Gregory wrote: > > > Didn't XZ change their Java reqs? > > XZ 1.7 was compiled with -target 9 and I asked whether this was an > intentional change. Turned out is was not and X

Re: [VOTE] Create new component commons-release-plugin

+1 Thanks very much. I hope, we'll all be reaping you works benefits soon. Jochen On Thu, Jan 4, 2018 at 6:34 PM, Gary Gregory wrote: > +1 > > Thank you Rob for leading the charge here. > > Gary > > On Thu, Jan 4, 2018 at 9:56 AM, Rob Tompkins wrote: > >> Hello all, >> >> I propose that we cr

Re: commons-compress git commit: Update XZ for Java dependency

On 2018-01-04, Gary Gregory wrote: > Didn't XZ change their Java reqs? XZ 1.7 was compiled with -target 9 and I asked whether this was an intentional change. Turned out is was not and XZ 1.8 changed the Java requirement back to 5. Kudos to Lasse Collin for pushing out the next release quickly.

Re: [VOTE] Create new component commons-release-plugin

+1 Thank you Rob for leading the charge here. Gary On Thu, Jan 4, 2018 at 9:56 AM, Rob Tompkins wrote: > Hello all, > > I propose that we create a new component [commons-release-plugin] to be > managed in the same fashion as the commons-build-plugin, and by that I mean: > > * Use COMMONSSITE a

Re: commons-compress git commit: Update XZ for Java dependency

Didn't XZ change their Java reqs? Gary On Thu, Jan 4, 2018 at 9:55 AM, wrote: > Repository: commons-compress > Updated Branches: > refs/heads/master ff5fb8a7a -> c3be6fb3d > > > Update XZ for Java dependency > > > Project: http://git-wip-us.apache.org/repos/asf/commons-compress/repo > Commit:

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

Hi Rob, I do not think we need a formal VOTE until we want to release, but why not. Reusing COMMONSITE makes sense for now. Go for it. Gary On Thu, Jan 4, 2018 at 9:51 AM, Rob Tompkins wrote: > > > > On Jan 4, 2018, at 11:45 AM, Gary Gregory > wrote: > > > > On Thu, Jan 4, 2018 at 9:43 AM, R

[VOTE] Create new component commons-release-plugin

Hello all, I propose that we create a new component [commons-release-plugin] to be managed in the same fashion as the commons-build-plugin, and by that I mean: * Use COMMONSSITE as the jira area * Create a git repo * Include it in the same portion of the site as the build-plugin (i.e. not a for

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

> On Jan 4, 2018, at 11:45 AM, Gary Gregory wrote: > > On Thu, Jan 4, 2018 at 9:43 AM, Rob Tompkins > wrote: > >> So with comments, I’m thinking I’ll submit a component vote. Any >> opposition? >> > > Do you already have a git repo, JIRA project and all that? Oh

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

On Thu, Jan 4, 2018 at 9:43 AM, Rob Tompkins wrote: > So with comments, I’m thinking I’ll submit a component vote. Any > opposition? > Do you already have a git repo, JIRA project and all that? Gary > > > On Jan 4, 2018, at 11:28 AM, Gary Gregory > wrote: > > > > That looks good. Thank you R

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

So with comments, I’m thinking I’ll submit a component vote. Any opposition? > On Jan 4, 2018, at 11:28 AM, Gary Gregory wrote: > > That looks good. Thank you Rob! > > Gary > >> On Thu, Jan 4, 2018 at 5:47 AM, Rob Tompkins wrote: >> >> @Gary - Below is the result from my release plugin with

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

I would be happy with a version 1 that only handles single module components. RERO! Gary On Thu, Jan 4, 2018 at 8:10 AM, Rob Tompkins wrote: > > > > On Jan 4, 2018, at 9:32 AM, Gilles wrote: > > > > On Thu, 4 Jan 2018 09:21:52 -0500, Rob Tompkins wrote: > >>> On Jan 4, 2018, at 9:18 AM, Gilles

Re: [commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

That looks good. Thank you Rob! Gary On Thu, Jan 4, 2018 at 5:47 AM, Rob Tompkins wrote: > @Gary - Below is the result from my release plugin with [lang3]. Give it a > looking over and let me know what you think. > > -Rob > > > On Jan 4, 2018, at 7:45 AM, chtom...@apache.org wrote: > > > > Auth

Re: [compress] TarArchiveEntry and Windows drive letter

On 2018-01-03, Torsten Curdt wrote: > I just found a new issue with compress. > It's the "normalizeFileName" in TarArchiveEntry again. > On Windows it just strips the drive letter > https://github.com/apache/commons-compress/blob/master/src/ > main/java/org/apache/commons/compress/archivers/tar/

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

> On Jan 4, 2018, at 9:32 AM, Gilles wrote: > > On Thu, 4 Jan 2018 09:21:52 -0500, Rob Tompkins wrote: >>> On Jan 4, 2018, at 9:18 AM, Gilles wrote: >>> >>> On Thu, 4 Jan 2018 08:56:09 -0500, Rob Tompkins wrote: > On Jan 4, 2018, at 8:41 AM, Gilles wrote: > > On Thu, 4 Jan 2018

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

On Thu, 4 Jan 2018 09:21:52 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 9:18 AM, Gilles wrote: On Thu, 4 Jan 2018 08:56:09 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 8:41 AM, Gilles wrote: On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 5:24 AM, Gilles wrot

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

> On Jan 4, 2018, at 9:18 AM, Gilles wrote: > > On Thu, 4 Jan 2018 08:56:09 -0500, Rob Tompkins wrote: >>> On Jan 4, 2018, at 8:41 AM, Gilles wrote: >>> >>> On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: > On Jan 4, 2018, at 5:24 AM, Gilles wrote: > > Hi. > >> O

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

On Thu, 4 Jan 2018 08:56:09 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 8:41 AM, Gilles wrote: On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 5:24 AM, Gilles wrote: Hi. On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: Hello all, So, now I have a plugin

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

> On Jan 4, 2018, at 8:41 AM, Gilles wrote: > > On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: >>> On Jan 4, 2018, at 5:24 AM, Gilles wrote: >>> >>> Hi. >>> On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: Hello all, So, now I have a plugin that detaches th

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

On Thu, 4 Jan 2018 08:08:05 -0500, Rob Tompkins wrote: On Jan 4, 2018, at 5:24 AM, Gilles wrote: Hi. On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: Hello all, So, now I have a plugin that detaches the distributions, zips the site, and then commits the zipped site, RELEASE-NOTES.txt

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

Yes. You can make those properties in the settings.xml, and if you’ve authenticated once with the svn server, you do not need to provide credentials. > On Jan 4, 2018, at 8:30 AM, Matt Benson wrote: > > Hi Rob, > I noticed that your sample usage included authentication credentials at the > com

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

On 4 January 2018 at 13:30, Matt Benson wrote: > Hi Rob, > I noticed that your sample usage included authentication credentials at the > command line. Does your work also support Maven settings-based > authentication specified in server XML elements? If not, there is some sample code you could li

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

Hi Rob, I noticed that your sample usage included authentication credentials at the command line. Does your work also support Maven settings-based authentication specified in server XML elements? Matt On Jan 4, 2018 7:08 AM, "Rob Tompkins" wrote: > > > > On Jan 4, 2018, at 5:24 AM, Gilles wrot

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

> On Jan 4, 2018, at 5:24 AM, Gilles wrote: > > Hi. > > On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: >> Hello all, >> >> So, now I have a plugin that detaches the distributions, zips the >> site, and then commits the zipped site, RELEASE-NOTES.txt (from the >> root), and the distrib

[commons-release-plugin) (Was: svn commit: r24009 - in /dev/commons/lang: ./ binaries/ source/)

@Gary - Below is the result from my release plugin with [lang3]. Give it a looking over and let me know what you think. -Rob > On Jan 4, 2018, at 7:45 AM, chtom...@apache.org wrote: > > Author: chtompki > Date: Thu Jan 4 12:45:36 2018 > New Revision: 24009 > > Log: > Staging release: commons-

Re: [commons-release-plugin] (Was: svn commit: r24003 - in /dev/commons/text: ./ binaries/ source/)

Hi. On Wed, 3 Jan 2018 21:07:41 -0500, Rob Tompkins wrote: Hello all, So, now I have a plugin that detaches the distributions, zips the site, and then commits the zipped site, RELEASE-NOTES.txt (from the root), and the distributions to the svn staging area. All from: mvn clean site deploy -Pre