I can do that after moving things over to the Maven standard directory structure (which will unfortunately validate the patch). But it is easy to recreate after the move anyway...
On Fri, Mar 6, 2009 at 12:43 PM, Kalle Korhonen <[email protected]>wrote: > Before renaming the packages, one of the devs should go through the JIRAs > and apply the patches that are safe and non-controversial (at least > https://issues.apache.org/jira/browse/KI-42 comes to mind). Later, it's > going to be more work for everybody. > > Kalle > > > On Fri, Mar 6, 2009 at 9:03 AM, Emmanuel Lecharny <[email protected] > >wrote: > > > David Jencks wrote: > > > >> > >> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote: > >> > >> I think it would be smart to change from org.jsecurity.* to > >>> org.apache.ki.* > >>> only immediately before our first Apache release. This allows our > >>> existing > >>> user community to avoid changing source code dependencies until > >>> absolutely > >>> necessary. > >>> > >>> I'm recommending this because there are a few people that regularly > build > >>> snapshots for trunk for integration testing (Grails plugin, et. al), > and > >>> I'd > >>> like to avoid any headache for them until absolutely required. > >>> > >>> Would this be ok? Any objections? What does everyone think? > >>> > >> > >> I'm inclined to think that changing the package names will result in a > >> great deal of breakage all over the place and doing it as soon as > possible > >> is more likely to result in a working first release. > >> > > Yeah, I share David vision... Recalls me the last time I differed a > dentist > > appointment :/ > > > > -- > > -- > > cordialement, regards, > > Emmanuel Lécharny > > www.iktek.com > > directory.apache.org > > > > > > >
