wicket-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nino Saturnino Martinez Vazquez Wael <nino.marti...@jayway.dk>
Subject rules for projects at wicket extensions/stuff/etc
Date Tue, 13 May 2008 18:55:00 GMT
And now that we are at it, what are the rules for when which project 
goes where, I've always been confused about it. What the rules for which 
projects goes where, and im thinking of wicket stuff, wicket core, 
wicket extensions, and something beside wicket extensions like spring, 
auth roles etc...

Could we clarify some rules about it? Something like that, even when 
trying to describe the rules for them I cant find out the logic.. And 
how should newcomers then feel?

Wicket stuff minis= small project / one behavior or something like that..

Wicket stuff seperate project = non core commiter and/or?

Wicket stuff in general = non apache compatible license.
----------------------------------------------------------------------------

Seperate project next to wicket extensions/spring/ioc etc = external 
dependencies?

Wicket Extensions = core comitter & maintainance plan?

Wicket Core= ?

-- 
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


Mime
View raw message