The main reason for keeping it around is that the latest stable release of Seam still uses it. But the idea of tagging + deleting is find by me.
BTW how do you split a Git repo? simply by cloning and removing what you don't want? On 17 janv. 2011, at 11:29, Hardy Ferentschik wrote: > Hi, > > I was wondering for quite some time what to do with the > hibernate-validator-legacy module of the current > Validator codebase. > It contains the old Validator 3.x code which originally wanted to keep > around. However, afaik there > was no activity against it for months if not even for years. > hibernate-validator-legacy slows down the overall build time, leads to > confusions when you are searching for > classes in the IDE and overall does not serve a real purpose. > > I see two alternatives. Create a final tag and remove the module or create > a new git repo and move the code into > there. Given that lack of activity I would suggest the first option. We > can cross the bridge of creating a repo > for it, if we ever decide for another legacy release. > > Thoughts? > > --Hardy > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
