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. Great advice again Martijn, thanks! On Thu, Jun 26, 2008 at 11:28 AM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Martijn Dashorst wrote: >> >>> This work too. Depends on the existing user's base, I guess ? >>> >> >> Which was in the thousands for Wicket at the time, with numerous >> systems in production. >> > > and it makes perfect sense to follow your way in this case. How many users > does JSecurity has ? > > Regarding the potential incubation failure, I would say that the cost of a > double migration will be overwhelmed by the killing effect of this failure. > It's a little bit like picking the lawyer to manage your divorce before the > wedding :). > > However, with thousands existing users, like for wicket, it makes sense too > (I don't know how many lawyers Bill Gates consulted before being married ;) > > At this point, the JSecurity team will have to make the best choice. > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
