Oops, I feel this hijacked Jukka's thread. So, what about the following Maven repo statement?
Incubating projects won't be published to the main repository under the org.apache group ID, but they are free to publish to other group ids of their choosing. This means existing projects that enter the incubator who already publish to the main repo would probably retain their source code packaging namespaces until the project graduates. Is that acceptable? On Thu, Jun 26, 2008 at 12:02 PM, Les Hazlewood <[EMAIL PROTECTED]> wrote: > Thanks to IntelliJ Idea, which updates our Spring and Hibernate files > automatically during refactoring already, even this isn't an issue for > us (thankfully). We should be good! > > On Thu, Jun 26, 2008 at 11:49 AM, Emmanuel Lecharny > <[EMAIL PROTECTED]> wrote: >> Les Hazlewood wrote: >>> >>> I don't know the exact usage, but I'm sure it is in lower thousands - >>> many people use our .jars directly, but probably many more use it via >>> 3rd party plugins (Grails plugin, etc) that is built on top of >>> JSecurity. >>> >>> It sounds as if waiting at the last possible second to move from >>> org.jsecurity.* to org.apache.jsecurity.* is the best option for us. >>> That way we can move over to the Apache SVN as soon as possible, but >>> impact the existing community only when absolutely necessary. >>> >> >> Sounds reasonnable too. Thanks to modern IDE, package renaming is just a >> matter of minutes (as soon as you don't forget to modify the Spring files - >> or any other container using class names - :) >> >> -- >> -- >> cordialement, regards, >> Emmanuel Lécharny >> www.iktek.com >> directory.apache.org >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
