Well, we just followed Gary and Benedikt recommendation to adopt the current components' style. For us as podling is fine whatever you decide, we just need a decision (an permission to deploy over it).
On Sun, May 3, 2015 at 9:33 PM, Phil Steitz <phil.ste...@gmail.com> wrote: > On 5/3/15 12:26 PM, Jochen Wiedmann wrote: > > On Sun, May 3, 2015 at 9:03 PM, Phil Steitz <phil.ste...@gmail.com> > wrote: > >> On 5/3/15 11:56 AM, Jochen Wiedmann wrote: > >>> On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández <wik...@apache.org> > wrote: > >>>> we're discussing our first incubating release, and we came to the > issue > >>>> that we are not grant with permissions to deploy maven artifacts to > the > >>>> org.apache.commons groupId [1]. > >>> Why org.apache.commons, and not, say, org.apache.commons.rdf? The > >>> former seems overly broad to me. > >> Could be we should have gone that way years ago when we moved to > >> org.apache.commons:commons-foo; but that ship has sailed, so I think > >> its best to stay consistent with the rest of the components and > >> proceed as proposed. > > > > First release, and the ship has sailed? Sorry, but I don't think so. > > What I meant was the decision to standardize on > > GroupId: org.apache.commons > ArtifactId: commons-foo[v] > > I am -1 for making new components different. > > Phil > > > > Jochen > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co
