commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <GGreg...@seagullsoftware.com>
Subject RE: [all] Rebooting commons projects
Date Wed, 13 May 2009 14:53:11 GMT
> -----Original Message-----
> From: Mark Struberg [mailto:struberg@yahoo.de]
> Sent: Wednesday, May 13, 2009 3:23 AM
> To: Commons Developers List
> Subject: AW: [all] Rebooting commons projects
> 
> 
> +1 for new packages
> -0 for x-ng
> 
> let's make 1 step back and see the issue from the distance.
> 
> What's currently going on is not a simple 'feature addition' which has to
> be compatible. It's more about an effort to use a lot of cool features
> which are available since java-5 _without_ having to take care about old
> 'ballast'.
> 
> So what about changing commons to commons5 for example?
> 
> e.g. org.apache.commons5.lang.Validate
> 
> This would have the benefit that everyone sees clearly what he get's!
> The groupId should also be changed to "org.apache.commons5".
> This would also be a good point to clean up the inhomogenic
> groupId/artifactId structure (commons-lang/commons-lang vs
> org.apache.commons/commons-lang)

Would we be happy to have also commons6 and commons7?

Gary

> 
> The projects may either remain in the same SVN (new branch) or a
> completely new one.
> Both have pros and cons we should discuss.
> 
> LieGrue,
> strub
> 
> 
> 
> ----- Ursprüngliche Mail ----
> > Von: Jörg Schaible <joerg.schaible@gmx.de>
> > An: dev@commons.apache.org
> > Gesendet: Mittwoch, den 13. Mai 2009, 07:57:14 Uhr
> > Betreff: Re: [all] Rebooting commons projects
> >
> > James Carman wrote at Mittwoch, 13. Mai 2009 04:30:
> >
> > > On Tue, May 12, 2009 at 9:38 PM, Dan Fabulich wrote:
> > >> If you feel like you'd want to call it "lang2" or "lang-ng" then just
> > >> call it lang 2.0 or 3.0 or whatever and keep a lang-1.x branch around
> for
> > >> stability fixes.
> > >
> > > I thought we agreed that we would "jump" major version numbers (as you
> > > suggest here I think) whenever we are going to break backwards
> > > compatibility (which would include "next generation" type changes).
> > > Then, we would change the package name to match to avoid the "jar
> > > hell" issue.
> >
> > +1
> >
> > > I don't like the "ng" stuff either.  What's next?  Commons Lang Deep
> > > Space 9?  :)  Doesn't a new major version number imply "next
> > > generation"?
> >
> > Hehehe ... reloaded? Fortunately we're forward bound, otherwise we would
> > additionally talk about "origins" :))
> >
> > - Jörg
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org


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


Mime
View raw message