I am a user of Wicket Security and I would prefer:

 [x] adopt Wicket security into Apache Wicket
 [] keep 
Wicket security at Wicket Stuff

best regards
giovanni





________________________________
From: Martin Grigorov <mcgreg...@e-card.bg>
To: users@wicket.apache.org
Cc: d...@wicket.apache.org
Sent: Fri, January 22, 2010 4:03:48 PM
Subject: Re: Future of Wicket Security (WASP/SWARM)

On Fri, 2010-01-22 at 10:52 +0100, Martijn Dashorst wrote:
> Guys,
> 
> I'd like to discuss the future of the Wicket Security project.
> Currently the project lives on/in the wicketstuff repository, but uses
> group id and package names "org.apache.wicket". IMO We should either:
> 
>  - adopt Wicket Security into the Wicket project and move everything
> over from Wicket Stuff into a subproject within Apache Wicket (and
> adopt the committers), or
>  - keep Wicket Security at wicketstuff and move it into the fold of
> wicket stuff, including groupid/package rename.
> 
> Since development on wicket security 1.4 is currently happening with a
> 1.4-beta1 just released, it is prudent to decide its future now (with
> a pending package rename).
> 
> Considering that both the wicket security contributors and the Wicket
> PMC members are needed to make this happen, all their opinions are
> considered binding.
> 
> [ ] adopt Wicket security into Apache Wicket
> [x] keep Wicket security at Wicket Stuff
I haven't seen in the mailing lists many users of it. Most of them use
Spring Security (my statistics).

I think there is no need to add one more thing to support by the core
committers.

P.S. I personally prefer Shiro.
> 
> Martijn
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


      

Reply via email to