Re: Future of Wicket Security (WASP/SWARM)
Martijn Dashorst wrote: [ ] adopt Wicket security into Apache Wicket [X] keep Wicket security at Wicket Stuff With all due respect to the library, I mostly just code it out myself. Regards, Erik. -- Erik van Oosten http://day-to-day-stuff.blogspot.com/
Re: Future of Wicket Security (WASP/SWARM)
Non binding. [x] adopt Wicket security into Apache Wicket OT: Maybe at some point adopting some of the best projects from Wicket Stuff (e.g. inMethod grid) might be good for the community as releases will be synchronized with releases of Wicket core. Ernesto On Fri, Jan 22, 2010 at 10:52 AM, Martijn Dashorst martijn.dasho...@gmail.com 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 [ ] keep Wicket security at Wicket Stuff Martijn
Re: Future of Wicket Security (WASP/SWARM)
Just a thought which has been on my mind for a while but it's triggered again by this vote. I consider wicketstuff to be a playground, where some projects are experimental - but there are also some projects which are more or fully mature and often used in production environments. Anyway I'm very hesitant to put wicketstuff projects inside production environments myself because of this playground impression. Also the wiki and/or the lack of documentation to me is a confirmation of this impression. So, maybe it's worth a discussion whether we want something in between, to indicate a (wicketstuff) project is production-ready, recommended by core committers, to have some sort of quality indicator, etc. etc. As for the current situation with Wasp/Swarm given the two choices I'd vote for adopting it into Apache Wicket. But the situation may be different if we have an alternative. Antoine On Fri, Jan 22, 2010 at 12:14 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Non binding. [x] adopt Wicket security into Apache Wicket OT: Maybe at some point adopting some of the best projects from Wicket Stuff (e.g. inMethod grid) might be good for the community as releases will be synchronized with releases of Wicket core. Ernesto On Fri, Jan 22, 2010 at 10:52 AM, Martijn Dashorst martijn.dasho...@gmail.com 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 [ ] keep Wicket security at Wicket Stuff Martijn
Re: Future of Wicket Security (WASP/SWARM)
[X] keep Wicket security at Wicket Stuff OT: Maybe at some point adopting some of the best projects from Wicket Stuff (e.g. inMethod grid) might be good for the community as releases will be synchronized with releases of Wicket core. I thought synchronized releases are the idea of WicketStuff Core [1] [1] http://wicketstuff.org/confluence/display/STUFFWIKI/WicketStuff+Core+-+Migration+Guide
Re: Future of Wicket Security (WASP/SWARM)
But... Is this happening in practice? E.g. just take a look at http://wicketstuff.org/maven/repository/org/wicketstuff/inmethod-grid/ Current Wicket release is 1.4.5. I do not see a 1.4.5 in there?? The best thing you could do now is grab the latest snapshot and hope nothings is broken Which is a pity because this is really a very nice component... The same might happen with other nice things in there... and in other places by the way. This might be scary for beginners and for people that want to have the assurance they are using official stuff. But this thread was about something else so I'll stop my rambling... Best, Ernesto On Fri, Jan 22, 2010 at 1:17 PM, Jonas barney...@gmail.com wrote: [X] keep Wicket security at Wicket Stuff OT: Maybe at some point adopting some of the best projects from Wicket Stuff (e.g. inMethod grid) might be good for the community as releases will be synchronized with releases of Wicket core. I thought synchronized releases are the idea of WicketStuff Core [1] [1] http://wicketstuff.org/confluence/display/STUFFWIKI/WicketStuff+Core+-+Migration+Guide
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
Re: Future of Wicket Security (WASP/SWARM)
[ ] adopt Wicket security into Apache Wicket [x] keep Wicket security at Wicket Stuff I am biased, yes, but I much prefer Shiro in my Wicket apps too :) - Les On Fri, Jan 22, 2010 at 10:03 AM, Martin Grigorov mcgreg...@e-card.bg wrote: 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
