Jörg, what about all older living projects which used to have own groups even, like commons-lang:commons-lang?
Could you point me to this boilerplate stuff you think off? Maybe we can improve this. I have no problem with moving the packages back, but I personally think this would á la long end up in confusing end users. LieGrue, strub ----- Original Message ----- > From: Jörg Schaible <joerg.schai...@gmx.de> > To: dev@commons.apache.org > Cc: > Sent: Friday, December 21, 2012 1:23 AM > Subject: Re: svn commit: r1424618 - in /commons/sandbox/privilizer/trunk: ./ > ant/ ant/lib/ ant/test/ example/ maven-plugin/ modules/ modules/privilizer/ > modules/privilizer/api/ > modules/privilizer/api/src/main/java/org/apache/commons/weaver/privilizer/ > modules/privi... > > Matt Benson wrote: > >> Mark, >> Thanks for driving this forward--as I mentioned to you privately, > I'll >> be >> mostly out of pocket through the new year. The groupId may warrant >> discussion; most Commons components are being targeted to >> org.apache.commons, though I think I understand what you're driving at >> here: [weaver] may have some unlimited number of sub(-sub*)-modules which >> may warrant oac.weaver as a groupId. > > Actually I think this is a bad idea. We manage all of our components as one > large group and should not break consistency here. I don't want to know what > > effect this also has on some of our boiler plates we use for the build. > > - Jörg > > > --------------------------------------------------------------------- > 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
