On Fri, Oct 24, 2008 at 11:23 AM, Emmanuel Lecharny <[EMAIL PROTECTED]>wrote:
> Peter Ledbrook wrote: > >> There's a lot of projects that will be java and security eventually. No >>> reason why jsecurity should take the general name as it's own. I >>> recommend >>> finding another name for it. For example we could have named Triplesec >>> jsecurity but we did not because it would violate this spoken policy. >>> >>> >> >> The name JSecurity has quite a bit of traction already in the Grails >> community, so I think there would have to be a very good reason for >> such a change. >> > Alex does not suggest that you change the name, but if you have to keep > JSecurity web site alive, then we have to find another name for the Apache > product (correct me if i'm wrong, Alex). > I'm saying a name other than JSecurity is needed. Alex
