I really don't know why we should even bother tagging the wicket stuff projects with a WICKET_1_1 tag. Each project has its own release cycle, and as such its own tagging mechanism. There is absolutely no reason to tag a non released project with WICKET_1_1. That code may not even compile with wicket 1.1!
Martijn
On 12/14/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
so the mentality is use cvs wicket-stuff at your own risk?
-IgorOn 12/14/05, Martijn Dashorst < [EMAIL PROTECTED]> wrote:The Wicket stuff modules weren't released at all, so there was NO NEED to do so. These are separate projects, with their own release cycle. Each of those projects could depend on a different version of wicket, depending on the speed of the maintainer.
So, there is no need to fix anything.
Martijn--On 12/13/05, Igor Vaynberg < [EMAIL PROTECTED]> wrote:after discussing on irc we found out that the actual problem was that we did not tag the wicket-stuff modules with WICKET_1_1 when we released. i think that should be done for future releases.
-IgorOn 12/13/05, Gili <[EMAIL PROTECTED]> wrote:Hi,
wicket-stuff has:
WICKET_1_1
WICKET_1_1_BRANCH
HEAD
head
which is rather confusing and inconsistent with the tags/branches in the "wicket" repository. Who is CVS admin for wicket-stuff? Can this be cleaned up?
Gili
--
http://www.desktopbeautifier.com/
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1
