Filed issue -> https://issues.apache.org/jira/browse/NPANDAY-383
Thanks, -- liit On Fri, Mar 25, 2011 at 2:21 PM, Lars Corneliussen <[email protected]>wrote: > I hate when group ids change :) > > But org.apache.npanday is a better one :) So i'm all 4 it. > > Could we also eliminate the extra groupids for plugins/netplugins i.e. > > -- > Message sent from mobile device > > Am 25.03.2011 um 05:18 schrieb Brett Porter <[email protected]>: > > > > > On 25/03/2011, at 2:50 PM, Adelita Padilla wrote: > > > >> Hi Everyone, > >> > >> > >> In the last release (1.3-incubating), the deployed artifacts were not > >> synched to central and it's because of the groupId (which was > "npanday"). > >> > >> > >> So before we proceed we the next release, we are proposing to change the > >> groupId from "npanday" to "org.apache.npanday". > >> > >> > >> Any comments/suggestions/reactions? > > > > I think it's important to do, we just need to be aware of the > implications. Plugin versions will no longer be mediated. Initially I wanted > to wait until 2.0 (as perhaps we could trim the list of plugins needed > anyway). However, I don't have any confidence in being able to get the > existing group ID into central and I think the additional repositories are > being a pain. > > > > However, I'll also note that the RDF artifacts aren't in central either, > so there is still configuration needed there anyway. If others feel strongly > that we shouldn't change for this release (and just not sync to central), > then I'm ok with that. > > > > - Brett > > > > > > -- > > Brett Porter > > [email protected] > > http://brettporter.wordpress.com/ > > http://au.linkedin.com/in/brettporter > > > > > > > > >
