Re: [discuss] Vote to git it?

This is the killer feature for Git, because many of us, the newcomers, like me, will want to experiment a little before submitting a patch. This way, I can create a local branch and I'm free to do whatever I want. The SVN branch is visible on the server, I don't want to publish my crappy code befor

Re: Nexus ACLs

I think I'll just upload the artifacts on people.apache.org and put the release to a vote. We can upload the release in Maven Central later. Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additio

Re: Nexus ACLs

I just voted for the issue. I suggest you enroll others to do the same. Gary On Tue, Sep 9, 2014 at 4:33 PM, Emmanuel Bourg wrote: > Le 09/09/2014 21:42, Benedikt Ritter a écrit : > > Any news here? > > Still waiting :( > > https://issues.apache.org/jira/browse/INFRA-8276 > > >

Re: Nexus ACLs

Le 09/09/2014 21:42, Benedikt Ritter a écrit : > Any news here? Still waiting :( https://issues.apache.org/jira/browse/INFRA-8276 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev

Re: Nexus ACLs

Any news here? 2014-08-31 7:44 GMT+02:00 Dan Tran : > is it a typo for 'stagin' at URL?? > > > > > On Sat, Aug 30, 2014 at 10:26 PM, Gary Gregory > wrote: > > > IIRC, I've seen this before when the group ID does not exist in Nexus. So > > you have to ask infra for help. > > > > Gary > > > > >

Re: svn commit: r1609898 - in /commons/proper/lang/trunk/src: main/java/org/apache/commons/lang3/math/NumberUtils.java test/java/org/apache/commons/lang3/math/NumberUtilsTest.java

Thanks! I've implemented the suggested improvement in revision 1623872. 2014-08-30 19:28 GMT+02:00 sebb : > On 12 July 2014 10:48, wrote: > > Author: britter > > Date: Sat Jul 12 09:48:13 2014 > > New Revision: 1609898 > > > > URL: http://svn.apache.org/r1609898 > > Log: > > LANG-1016: NumberUt

Re: svn commit: r1610106 - /commons/proper/commons-parent/trunk/pom.xml

you mean like http://docs.oracle.com/javase/${maven.compiler.source}/docs/api/ ? 2014-08-30 19:22 GMT+02:00 sebb : > On 13 July 2014 03:36, wrote: > > Author: ggregory > > Date: Sun Jul 13 02:36:20 2014 > > New Revision: 1610106 > > > > URL: http://svn.apache.org/r1610106 > > Log: > > Make the

Re: [fileupload][daemon][beanutils] Missing Security Info in Website

Hello Stefan, this is a good idea. I think you've searched hard enough and the said components simply don't have such a page (yet). br, Benedikt 2014-08-31 13:16 GMT+02:00 Stefan Bodewig : > Hi all, > > I've put together a security page for Commons so people have a place to > get information qu

Re: [discuss] Vote to git it?

I'm fine with git. I was thinking about starting a discussion about migrating [lang] to git, anyway :-) 2014-09-09 15:10 GMT+02:00 Gary Gregory : > Should we vote to move Commons to git one component at a time (as Math just > has), or just vote to move them all at once and be done with it and the

Re: [discuss] Vote to git it?

Le 09/09/2014 21:02, Oliver Heger a écrit : > > > On 09.09.2014 19:56, Luc Maisonobe wrote: >> Le 09/09/2014 15:17, sebb a écrit : >>> On 9 September 2014 14:10, Gary Gregory wrote: Should we vote to move Commons to git one component at a time (as Math just has), or just vote to m

Re: [discuss] Vote to git it?

On 09/09/2014 18:40, Mark Fortner wrote: Schalk, The only problem I see with the way that you do code reviews on Github, is the fact that you can only review change sets. You can't simply go through an existing codebase and point out the problems. I suggested Stash and Crucible since they're bo

Re: [discuss] Vote to git it?

On 09.09.2014 19:56, Luc Maisonobe wrote: Le 09/09/2014 15:17, sebb a écrit : On 9 September 2014 14:10, Gary Gregory wrote: Should we vote to move Commons to git one component at a time (as Math just has), or just vote to move them all at once and be done with it and the inevitable? I thi

Re: [pool] POOL-272: per-key numTestsPerEvictionRun

Great, thanks! I have all the new config property boilerplate in place and I understand how it should work, but I'm debating the best way to implement the per-key queues. It would be nice if the test iteration for each key resumed in the same place the next time the cycle hits that key, but this im

Re: [discuss] Vote to git it?

Paul, Git branching is faster, computationally cheaper, and requires less disk space than svn branching. This link provides more information: https://git.wiki.kernel.org/index.php/GitSvnComparison. In git, you have a remote repo, and a local repo. Typically, people create local branches for expe

Re: [discuss] Vote to git it?

Le 09/09/2014 15:17, sebb a écrit : > On 9 September 2014 14:10, Gary Gregory wrote: >> Should we vote to move Commons to git one component at a time (as Math just >> has), or just vote to move them all at once and be done with it and the >> inevitable? > > I think it is far too early to decide.

Re: [discuss] Vote to git it?

Mark, can you help me understand why git branches (the "feature" branch) is better than an svn branch? Cheers, Paul On Tue, Sep 9, 2014 at 10:57 AM, Mark Fortner wrote: > If I had to pick one feature that makes git more useful than svn, it would > be the ease in creating feature branches. If

Re: [discuss] Vote to git it?

Schalk, The only problem I see with the way that you do code reviews on Github, is the fact that you can only review change sets. You can't simply go through an existing codebase and point out the problems. I suggested Stash and Crucible since they're both linked with JIRA, and I think Apache has

Re: [discuss] Vote to git it?

On 09/09/2014 16:57, Mark Fortner wrote: If I had to pick one feature that makes git more useful than svn, it would be the ease in creating feature branches. If you want to add a feature, you simply create a local branch to implement the feature, implement it, and commit it, and create a pull re

Re: [discuss] Vote to git it?

Gary, One thing that is a PITA is when getting pull requests from GitHub. The GH patches are not usable as it. Atlassian's Stash makes that easier to deal with. This video describes a fork-based workflow using Stash, and shows you how code reviews work. It also means that people can contribute

Re: [discuss] Vote to git it?

If I had to pick one feature that makes git more useful than svn, it would be the ease in creating feature branches. If you want to add a feature, you simply create a local branch to implement the feature, implement it, and commit it, and create a pull request. If you're using Atlassian's Crucibl

Re: [discuss] Vote to git it?

On Tue, Sep 9, 2014 at 11:27 AM, Emmanuel Bourg wrote: > Le 09/09/2014 16:52, Paul Benedict a écrit : > > Is there an itch to scratch (need) by moving to git as opposed to just > > continue using svn? > > I guess the "itch" is simply an increasing preference for Git among the > people involved he

Re: [discuss] Vote to git it?

Le 09/09/2014 16:52, Paul Benedict a écrit : > Is there an itch to scratch (need) by moving to git as opposed to just > continue using svn? I guess the "itch" is simply an increasing preference for Git among the people involved here. I don't think the migration will fix any important problem. Emm

Re: [discuss] Vote to git it?

On 9 September 2014 16:05, Emmanuel Bourg wrote: > Le 09/09/2014 16:49, sebb a écrit : > >> But AFAIK, there is not yet any Commons documentation on how to do >> things in Git. >> Nor what conventions we should use where there are different ways to do >> things. > > The development workflow is an

Re: [discuss] Vote to git it?

Le 09/09/2014 16:35, Gary Gregory a écrit : > I started this thread to get a feel for it. Some folks have a lot of > experience with git, some have none. Most of us here know Subversion 'by > default'. Understanding that and the comfort of folks of do not know git > and their willingness to get in

Re: [discuss] Vote to git it?

Le 09/09/2014 16:49, sebb a écrit : > But AFAIK, there is not yet any Commons documentation on how to do > things in Git. > Nor what conventions we should use where there are different ways to do > things. The development workflow is another topic, but I don't think we should change our habits.

Re: [discuss] Vote to git it?

Is there an itch to scratch (need) by moving to git as opposed to just continue using svn? Cheers, Paul On Tue, Sep 9, 2014 at 9:49 AM, sebb wrote: > On 9 September 2014 15:32, Gary Gregory wrote: > > On Tue, Sep 9, 2014 at 9:17 AM, sebb wrote: > > > >> On 9 September 2014 14:10, Gary Gregor

Re: [discuss] Vote to git it?

On 9 September 2014 15:32, Gary Gregory wrote: > On Tue, Sep 9, 2014 at 9:17 AM, sebb wrote: > >> On 9 September 2014 14:10, Gary Gregory wrote: >> > Should we vote to move Commons to git one component at a time (as Math >> just >> > has), or just vote to move them all at once and be done with i

Re: [discuss] Vote to git it?

On Tue, Sep 9, 2014 at 9:17 AM, Emmanuel Bourg wrote: > Le 09/09/2014 15:10, Gary Gregory a écrit : > > Should we vote to move Commons to git one component at a time (as Math > just > > has), or just vote to move them all at once and be done with it and the > > inevitable? > > I'm fine with both

Re: [discuss] Vote to git it?

On Tue, Sep 9, 2014 at 9:17 AM, sebb wrote: > On 9 September 2014 14:10, Gary Gregory wrote: > > Should we vote to move Commons to git one component at a time (as Math > just > > has), or just vote to move them all at once and be done with it and the > > inevitable? > > I think it is far too ear

Re: [discuss] Vote to git it?

On 9 September 2014 14:10, Gary Gregory wrote: > Should we vote to move Commons to git one component at a time (as Math just > has), or just vote to move them all at once and be done with it and the > inevitable? I think it is far too early to decide. Math has yet to start using git in earnest.

Re: [discuss] Vote to git it?

Le 09/09/2014 15:10, Gary Gregory a écrit : > Should we vote to move Commons to git one component at a time (as Math just > has), or just vote to move them all at once and be done with it and the > inevitable? I'm fine with both solutions. Do we have a consensus to migrate the components now? Emm

[discuss] Vote to git it?

Should we vote to move Commons to git one component at a time (as Math just has), or just vote to move them all at once and be done with it and the inevitable? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [DRAFT] Apache Commons Board Report, September 9 2014

Thank you Luc and Benedikt for your feedback. I've sent the report. Gary On Tue, Sep 9, 2014 at 8:25 AM, Gary Gregory wrote: > Will do. > > Thank you, > Gary > > On Tue, Sep 9, 2014 at 3:20 AM, Benedikt Ritter > wrote: > >> Hello Gary, >> >> how about reporting about the [math] git migration?

Re: [DRAFT] Apache Commons Board Report, September 9 2014

Will do. Thank you, Gary On Tue, Sep 9, 2014 at 3:20 AM, Benedikt Ritter wrote: > Hello Gary, > > how about reporting about the [math] git migration? > > Regards, > Benedikt > > 2014-09-08 16:07 GMT+02:00 Gary Gregory : > > > Please provide feedback as you see fit. I'll send this out in 24 hour

Re: [DRAFT] Apache Commons Board Report, September 9 2014

Hello Gary, how about reporting about the [math] git migration? Regards, Benedikt 2014-09-08 16:07 GMT+02:00 Gary Gregory : > Please provide feedback as you see fit. I'll send this out in 24 hours. > > > [DRAFT] Apache Commons Board Report, September 9 2014 > > > The Apache Commons project focu