> > Now I write this that creates even more issues, what if there is a critical > issue in wicketstuff that needs to push the version number? Should it > become 1.4.9.1 or 1.4.10? > > This was always the issue with the matching release numbers. But, since most projects in wicketstuff are hardly maintained and almost never receiving real "releases", there has not been a real need to push an "emergency release". Most people who are going to use wicketstuff stuff in their apps are content building it - because they've had to for years. So, the numbering is primarily to make it easy for newbs to Wicket to easily add WS projects that they know will compile against their version of Wicket.
-- Jeremy Thomerson http://www.wickettraining.com
