Some time ago I sent an email saying that I had created a CACTUS_v1x branch
in CVS so that development could continue on Cactus 1.x and that everything
related to Cactus v2 will happen on the main trunk. Now that I am ready to
commit some code that I have written for Cactus v2, I think this is the
wrong approach ...
Cactus v2 has been rewritten from scratch (of course reusing some parts of
Cactus v1 !) and I would like it to be considered as a proposal for the time
being until we demonstrate that it works, is easy to use, ... And also there
is still a lot of work to be continued and done on Cactus v1 : support for
tag libs, EJBs, documentation improvements, ...
Here is what I suggest :
- forget about the branches. We continue to develop Cactus 1.x on the main
trunk (I'll do the changes to CVS in order to merge the changes on the 1x
branch to the main trunk (that won't be a problem as I have not committed
anything related to Cactus v2 on the main trunk yet !).
- create a 'proposal' directory in jakarta-commons/cactus and put Cactus v2
there :
jakarta-commons
|_ beanutils
|_ ...
|_ cactus
|_ build
|_ src
|_ ...
|_ proposal
|_ cactus2
|_ src
|_ build
|_ ...
Anyone against this ? I will do it later today if noone objects ...
Thanks
-Vincent
