Re: [ALL] Who want's access to @ApacheCommons

2017-12-30 Thread Sergio Fernández 
On Dec 30, 2017 12:01, "Benedikt Ritter"  wrote:

> Am 27.12.2017 um 18:10 schrieb Sergio Fernández :
> I'm happy to help on that, but I'm just a raw committer, not sure if it
> would be appropriate.

Sure thing! Just give me your twitter handle and I’ll add you.


@wikier

Re: [collections] toward 4.2

2017-12-30 Thread Gary Gregory 
On Dec 30, 2017 03:55, "Benedikt Ritter"  wrote:

Hi,

+1! We should finally get COLLECTIONS-653 out of the door.


Do you mean that the Javado is Java-8-clean?

Gary


Benedikt

> Am 29.12.2017 um 18:58 schrieb Gary Gregory :
>
> Hi All,
>
> Does anyone want to fix some issues for 4.2? I am thinking of pushing out
> an RC soon.
>
> This is what we have so far:
>
>  
>
>  Unit tests MapUtilsTest and ListIteratorWrapperTest no longer fail on
> Java 9.
>
>
>  Intermittent test failures in Windows for HashSetValuedHashMap.
>
>
>  Uncomment test in AbstractMapTest regarding LRUMap equals.
>
>
>  Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility.
>
>
>  Fix site build on Java 8.
>
>
>  Update Javadoc to Build on Java 1.8.
>
>
>  Build status, Coverage status and Maven central weren't in README.md
>
>
>  Improve efficiency of DefaultedMap.get.
>
>
>  Small improvements for generics, conditional statements, and warnings
> suppressions.
>
>
>  Update platform from Java 6 to Java 7.
>
>
>  Web site spelling error: MultiValuedMapeList.
>
> due-to="Enrique">
>   Correction of Javadoc for
> org.apache.commons.collections4.functors.CatchAndRethrowClosure.
>
>
>  Add null-safe MapUtils.size(Map?, ?>) method.
>
> due-to="Shailender Bathula, Gary Gregory">
>  PatriciaTrie prefixMap clear throws NullPointerException.
>
>
>  Add class SortedProperties to sort keys.
>
>  
>
> Gary


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

Re: [commons-release-plugin] Progress report. (Was: Re: Questions regarding improving the Apache Commons release process.)

2017-12-30 Thread Gary Gregory 
Thank you for spearheading making our release process better.

One tricky thing to watch out for are components like Lang and DBCP which
have folder names on dist that are not the artifact ID. IOW lang vs lang3,
dbcp vs dbcp2.

Gary

On Dec 30, 2017 08:29, "Rob Tompkins"  wrote:

> Hello all,
>
> I just wanted to let everyone know where I’ve been running lately. I’m
> writing a new commons component specifically “commons-release-plugin” for
> the sake of making a maven plugin that adheres to our release process. I’m
> sandboxing it in my git work area:
>
> https://github.com/chtompki/commons-release-plugin <
> https://github.com/chtompki/commons-release-plugin>
>
> My goal is to get it functional an then bring it up for vote on creating
> it as a full fledged component (in the same vein as the
> commons-build-plugin).
>
> Currently, I have it declared locally in [text] with:
>
> org.apache.commons
> commons-release-plugin
> 0.1-SNAPSHOT
> 
>   scm:svn:https://dist.apache.org/repos/
> dist/dev/commons/text
> 
> 
>   
> detatch-assemblies
> verify
> 
>   detatch-assemblies
> 
>   
> 
>   
>
> immediately following this line: https://github.com/apache/
> commons-text/blob/master/pom.xml#L164  commons-text/blob/master/pom.xml#L164> in the pom. As it stands now, it
> detaches the distributions from the deployment to nexus (after gpg signing,
> and then copies them and the sha1’s and md5’s into a working directory in
> /target), My plan here is to use the maven-release-plugin as a guideline
> for how to publish these up to the dist svn repository. I think I’m further
> going to set up a mojo to do site deployment to somewhere (open to thoughts
> on where the site should go, maybe the dist svn area in a zip file like
> what Gary did with the latest [dbcp] release??).
>
> Given this is a progress report. I’m open to anyone telling me that I’m
> wasting my time and pointing me in a new direction.
>
> Cheers,
> -Rob
>
> P.S. I haven’t figured out how to write tests for maven plugins, so I have
> no testing in the project. I’m open to suggestions/help in that department
> if anyone wants to chip in and help.
>
>
> > On Dec 28, 2017, at 4:05 AM, Hervé BOUTEMY 
> wrote:
> >
> > Hi Rob,
> >
> > one additional point: currently, for Maven itself, instead of adding new
> > Maven-specific ReleasePhase(s) to the default configuration, or
> configure them in
> > our parent pom (I'm not sure documentation on how to do that is
> available: I
> > could not find it), we chose first to create a separate "dist-tool" to
> check
> > consistency of what is currently published in misc places and provide
> some
> > commands to fix when an inconsistency is found.
> >
> > This happens through daily reports done by a Jenkins job [1]:
> > - distribution area vs Maven Central [2]
> > - version from Maven site vs Maven Central [3]
> >
> > We did not produce any release nor made it really configurable for
> conventions
> > different from Maven ones (like Common's -src & -bin), but at least
> there is a
> > configuration file to define artifacts to check [4]
> >
> > HTH
> >
> > Hervé
> >
> >
> > [1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/
> >
> > [2] https://builds.apache.org/view/M-R/view/Maven/job/dist-
> tool-plugin/site/
> > dist-tool-check-source-release.html
> >
> > [3] https://builds.apache.org/view/M-R/view/Maven/job/dist-
> tool-plugin/site/
> > dist-tool-check-index-page.html
> >
> > [4] https://builds.apache.org/view/M-R/view/Maven/job/dist-
> tool-plugin/site/
> > dist-tool.conf.html
> >
> > Le mercredi 27 décembre 2017, 23:32:49 CET Rob Tompkins a écrit :
> >> Stephen,
> >>
> >> I can’t thank you enough for your reply. I’ll take your suggestions and
> >> continue to sandbox around using the maven-release-plugin as a
> guideline.
> >>
> >> All the best and happy holidays,
> >> -Rob
> >>
> >>> On Dec 26, 2017, at 5:27 AM, Stephen Connolly
> >>>  wrote:>
> >>> On Tue 26 Dec 2017 at 03:10, Rob Tompkins  > > wrote:
>  Hello all,
> 
>  Pardon, maybe this should have gone to your @user list, but why not
> ping
>  the dev crew. I’ve been playing around the ideas surrounding our
> fairly
>  manual release process for the components in Commons, and I was hoping
>  for
>  some insights.
> 
>  Scripting the version changes isn’t really that big of a deal for us,
> and
>  that I can manage. But, when it comes to publishing our artifacts to
> the
>  apache nexus repository, and then separately publishing our -src and
> -bin
>  assemblies to the dev dist subversion repository (and consequently
>  deleting
>  those artifacts from nexus as they’re “attached” for the

[commons-release-plugin] Progress report. (Was: Re: Questions regarding improving the Apache Commons release process.)

2017-12-30 Thread Rob Tompkins 
Hello all,

I just wanted to let everyone know where I’ve been running lately. I’m writing 
a new commons component specifically “commons-release-plugin” for the sake of 
making a maven plugin that adheres to our release process. I’m sandboxing it in 
my git work area:

https://github.com/chtompki/commons-release-plugin 


My goal is to get it functional an then bring it up for vote on creating it as 
a full fledged component (in the same vein as the commons-build-plugin).

Currently, I have it declared locally in [text] with:

org.apache.commons
commons-release-plugin
0.1-SNAPSHOT

  
scm:svn:https://dist.apache.org/repos/dist/dev/commons/text


  
detatch-assemblies
verify

  detatch-assemblies

  

  

immediately following this line: 
https://github.com/apache/commons-text/blob/master/pom.xml#L164 
 in the pom. 
As it stands now, it detaches the distributions from the deployment to nexus 
(after gpg signing, and then copies them and the sha1’s and md5’s into a 
working directory in /target), My plan here is to use the maven-release-plugin 
as a guideline for how to publish these up to the dist svn repository. I think 
I’m further going to set up a mojo to do site deployment to somewhere (open to 
thoughts on where the site should go, maybe the dist svn area in a zip file 
like what Gary did with the latest [dbcp] release??).

Given this is a progress report. I’m open to anyone telling me that I’m wasting 
my time and pointing me in a new direction.

Cheers,
-Rob

P.S. I haven’t figured out how to write tests for maven plugins, so I have no 
testing in the project. I’m open to suggestions/help in that department if 
anyone wants to chip in and help.


> On Dec 28, 2017, at 4:05 AM, Hervé BOUTEMY  wrote:
> 
> Hi Rob,
> 
> one additional point: currently, for Maven itself, instead of adding new 
> Maven-specific ReleasePhase(s) to the default configuration, or configure 
> them in 
> our parent pom (I'm not sure documentation on how to do that is available: I 
> could not find it), we chose first to create a separate "dist-tool" to check 
> consistency of what is currently published in misc places and provide some 
> commands to fix when an inconsistency is found.
> 
> This happens through daily reports done by a Jenkins job [1]:
> - distribution area vs Maven Central [2] 
> - version from Maven site vs Maven Central [3]
> 
> We did not produce any release nor made it really configurable for 
> conventions 
> different from Maven ones (like Common's -src & -bin), but at least there is 
> a 
> configuration file to define artifacts to check [4]
> 
> HTH
> 
> Hervé
> 
> 
> [1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/
> 
> [2] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> dist-tool-check-source-release.html
> 
> [3] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> dist-tool-check-index-page.html
> 
> [4] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> dist-tool.conf.html
> 
> Le mercredi 27 décembre 2017, 23:32:49 CET Rob Tompkins a écrit :
>> Stephen,
>> 
>> I can’t thank you enough for your reply. I’ll take your suggestions and
>> continue to sandbox around using the maven-release-plugin as a guideline.
>> 
>> All the best and happy holidays,
>> -Rob
>> 
>>> On Dec 26, 2017, at 5:27 AM, Stephen Connolly
>>>  wrote:> 
>>> On Tue 26 Dec 2017 at 03:10, Rob Tompkins  > wrote:
 Hello all,
 
 Pardon, maybe this should have gone to your @user list, but why not ping
 the dev crew. I’ve been playing around the ideas surrounding our fairly
 manual release process for the components in Commons, and I was hoping
 for
 some insights.
 
 Scripting the version changes isn’t really that big of a deal for us, and
 that I can manage. But, when it comes to publishing our artifacts to the
 apache nexus repository, and then separately publishing our -src and -bin
 assemblies to the dev dist subversion repository (and consequently
 deleting
 those artifacts from nexus as they’re “attached” for the purpose of gpg
 signing), I feel it a tad cumbersome.
 
 I’ve fiddled around a little with the idea of detaching the -src and -bin
 assemblies after gpg signing with some success, but then I have to delve
 into the mechanics of publishing those up to the subversion repository,
 and
 clearly that problem has already been solved.
>>> 
>>> Is your problem you don’t want those going to Nexus staging but only to
>>> dist? Or is it that you want them *also* going to dist.
>>> 
>>>

Re: [beanutils] Moving to beanutils2

2017-12-30 Thread Gary Gregory 
Who can speak to that code base?

Gary

On Dec 30, 2017 03:54, "Benedikt Ritter"  wrote:

>
>
> > Am 29.12.2017 um 19:58 schrieb Gary Gregory :
> >
> > On Wed, Dec 27, 2017 at 11:55 AM, Gary Gregory 
> > wrote:
> >
> >> The changes for:
> >>
> >> BEANUTILS-500 Upgrade commons-collections to 4
> >>
> >> break BC (see BEANUTILS-500).
> >>
> >> Therefore, I created BEANUTILS-503: Change packaging from
> >> org.apache.commons.beanutils to org.apache.commons.beanutils2
> >>
> >> This change should happen sooner rather than later IMO to allow folks
> >> using SNAPSHOT builds to adapt.
> >>
> >> Thoughts?
> >>
> >
> > This is done is SVN trunk.
>
> We already have a complete rewrite of the BeanUtils API in the sandbox
> [1]. What do we want to do with that?
>
> Regards,
> Benedikt
>
> [1] http://svn.apache.org/viewvc/commons/sandbox/beanutils2/trunk/
>
> >
> > Gary
> >
> >
> >>
> >> Gary
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

AW: [commons-lang3] NumberUtils feature

2017-12-30 Thread jhm 
Maybe open the comparators and use a fluent API?
is(42).between(10).and(50) == true
is(10).between(10).and(20) == false
is(10).between(10).and(20).includingLeft() == true
is(50).between(10).and(50) == false
is(50).between(10).and(50).includingRight() == true


Just quick thoughts ...

Jan


> -Ursprüngliche Nachricht-
> Von: Gilles [mailto:gil...@harfang.homelinux.org]
> Gesendet: Freitag, 29. Dezember 2017 22:46
> An: dev@commons.apache.org
> Betreff: Re: [commons-lang3] NumberUtils feature
> 
> On Fri, 29 Dec 2017 16:19:05 -0200, Lucas Carvalho wrote:
> > Gilles, thanks for you reply.
> >
> > I will consider your sugestions.
> >
> > So, can i open a issue in jira (apache commons) and implement this
> > feature?
> 
> Better wait for other opinions on the various suggestions, as it
> impacts on which JIRA project you'd open the issue.
> 
> Regards,
> Gilles
> 
> >
> > Thanks.
> >
> > Lucas Carvalho
> >
> >
> >
> > On Fri, Dec 29, 2017 at 12:25 PM, Gilles
> > 
> > wrote:
> >
> >> Hi.
> >>
> >> On Fri, 29 Dec 2017 11:53:29 -0200, Lucas Carvalho wrote:
> >>
> >>> I`m sorry,
> >>>
> >>> Now code in "text":
> >>>
> >>> public static boolean between(final int value, final int x, final
> >>> int y) {
> >>>
> >>>return value >= x && value <= y;
> >>>
> >>> }
> >>>
> >>>
> >>> public static boolean between(final short value, final short x,
> >>> final short
> >>> y) {
> >>>
> >>>return value >= x && value <= y;
> >>>
> >>> }
> >>>
> >>
> >> To comply with the Java convention, it should probably be
> >> "isBetween".
> >>
> >> Incidently, this also shows a weakness of "Utils" classes: the
> >> "target"
> >> (which would normally be "this") is on the same footing as the other
> >> arguments (the bounds of the interval here).
> >>
> >> Also the naming does not reflect whether bounds are included or not:
> >> usually, one would assume that the left bound is included (>=) but
> >> not the right one (<).
> >>
> >> Then, what about "between(15, 20, 10)"?
> >>
> >> Finally, we should consider whether to continue bloating
> >> "NumberUtils"
> >> in "Lang" or move some of it to the new "Numbers" component.[1]
> >>
> >> Regards,
> >> Gilles
> >>
> >> [1]
> >> https://git1-us-west.apache.org/repos/asf?p=commons-
> numbers.git;a=tre
> >> e
> >>
> >>
> >>>
> >>>
> >>> Obrigado.
> >>>
> >>> Atenciosamente
> >>>
> >>> Lucas Carvalho
> >>>
> >>> *Fone *- 34 9 9903 4621
> >>>
> >>> On Fri, Dec 29, 2017 at 11:47 AM, Gilles
> >>> 
> >>> wrote:
> >>>
> >>> Hi.
> 
>  On Fri, 29 Dec 2017 09:51:59 -0200, Lucas Carvalho wrote:
> 
>  Hello everybody,
> >
> > I want know if the feature "between" in NumberUtils lib has be
> > discussed?
> > I
> > use this methods a lot and i would like to share this code in
> > apache commons.
> >
> > Below i share a example:
> >
> > [image: Inline image 1]
> >
> >
>  All I can see is the above.
>  [Perhaps the image was stripped.]
> 
>  I assume it is code; so, please write it here as "text".
> 
>  Thanks,
>  Gilles
> 
> 
>  Thanks.
> >
> > Lucas Carvalho
> 
> 
> -
> 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] Who want's access to @ApacheCommons

2017-12-30 Thread Benedikt Ritter 
Hi,

> Am 27.12.2017 um 18:10 schrieb Sergio Fernández :
> 
> I guess if the people managing the account could just RT the
> project-related tweets (particularly announcements), I think that would be
> great.
> 
> I'm happy to help on that, but I'm just a raw committer, not sure if it
> would be appropriate.

Sure thing! Just give me your twitter handle and I’ll add you.

Benedikt

> 
> On Tue, Dec 26, 2017 at 2:22 AM, Benedikt Ritter  wrote:
> 
>> Hi,
>> 
>> I’ve created the Apache Commons twitter account [1] a few years ago. I try
>> to announce anything that might be of interest for Commons users. Since my
>> activity for the project varies a bit depending on what is going on in my
>> life, I think it would be good if more people would have access to the
>> twitter account.
>> Twitter has ha nice feature, called Teams, where you can give other
>> Twitter users access to a team account. So if anybody wants to have access,
>> just ping me with your Twitter user name and I can grant you access.
>> 
>> Regards,
>> Benedikt
>> 
>> [1] https://twitter.com/ApacheCommons
>> 
>> 
>> -
>> 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: [beanutils] Toward 2.0.0

2017-12-30 Thread Benedikt Ritter 
Hi,

> Am 28.12.2017 um 20:49 schrieb Gary Gregory :
> 
> Hi All,
> 
> - BeanUtils now has a new package o.a.c.beanutils2.
> - BeanUtils now depends on Apache Commons Collection 4 (instead of 3),
> which caused the above.
> 
> What more do we want before releasing 2.0.0?
> 
> Updating from BU 1.x to 2.x should be "simple" for now: Just update your
> imports.
> 
> Thoughts?

See my comment on the other thread. What about the BeanUtils rewrite we have in 
the Sandbox?

> 
> Gary


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

Re: [collections] toward 4.2

2017-12-30 Thread Benedikt Ritter 
Hi,

+1! We should finally get COLLECTIONS-653 out of the door.

Benedikt

> Am 29.12.2017 um 18:58 schrieb Gary Gregory :
> 
> Hi All,
> 
> Does anyone want to fix some issues for 4.2? I am thinking of pushing out
> an RC soon.
> 
> This is what we have so far:
> 
>  
>
>  Unit tests MapUtilsTest and ListIteratorWrapperTest no longer fail on
> Java 9.
>
>
>  Intermittent test failures in Windows for HashSetValuedHashMap.
>
>
>  Uncomment test in AbstractMapTest regarding LRUMap equals.
>
>
>  Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility.
>
>
>  Fix site build on Java 8.
>
>
>  Update Javadoc to Build on Java 1.8.
>
>
>  Build status, Coverage status and Maven central weren't in README.md
>
>
>  Improve efficiency of DefaultedMap.get.
>
>
>  Small improvements for generics, conditional statements, and warnings
> suppressions.
>
>
>  Update platform from Java 6 to Java 7.
>
>
>  Web site spelling error: MultiValuedMapeList.
>
> due-to="Enrique">
>   Correction of Javadoc for
> org.apache.commons.collections4.functors.CatchAndRethrowClosure.
>
>
>  Add null-safe MapUtils.size(Map?, ?>) method.
>
> due-to="Shailender Bathula, Gary Gregory">
>  PatriciaTrie prefixMap clear throws NullPointerException.
>
>
>  Add class SortedProperties to sort keys.
>
>  
> 
> Gary


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

Re: [beanutils] Moving to beanutils2

2017-12-30 Thread Benedikt Ritter 


> Am 29.12.2017 um 19:58 schrieb Gary Gregory :
> 
> On Wed, Dec 27, 2017 at 11:55 AM, Gary Gregory 
> wrote:
> 
>> The changes for:
>> 
>> BEANUTILS-500 Upgrade commons-collections to 4
>> 
>> break BC (see BEANUTILS-500).
>> 
>> Therefore, I created BEANUTILS-503: Change packaging from
>> org.apache.commons.beanutils to org.apache.commons.beanutils2
>> 
>> This change should happen sooner rather than later IMO to allow folks
>> using SNAPSHOT builds to adapt.
>> 
>> Thoughts?
>> 
> 
> This is done is SVN trunk.

We already have a complete rewrite of the BeanUtils API in the sandbox [1]. 
What do we want to do with that?

Regards,
Benedikt

[1] http://svn.apache.org/viewvc/commons/sandbox/beanutils2/trunk/

> 
> Gary
> 
> 
>> 
>> Gary
>> 


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

Re: [compress] ZstdCompressorInputStreamTest failure

2017-12-30 Thread Stefan Bodewig 
On 2017-12-30, Gary Gregory wrote:

> With git master, I get:

>  ZstdCompressorInputStreamTest.testZstdDecode:59 arrays first differed at
> element [70]; expected:<13> but was:<10>

> Anyone else?

Passes for me and Jenkins (even the Windows builds).

My guess is your working copy has Windows lineends in the zstd
compressed file. I've just updated .gitattributes so if your version of
git honors it you can apply it to your existing working copy by pulling,
removing .git/index and then running "git reset --hard".

Stefan

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