Hi,
I'm definitely for removing the legacy project, too. Given it will very
likely never change again I think a new repo for it would do more harm than
good, so I'm also preferring option 1.
If it is for any reason still needed for Seam or similar we might remove the
legacy module from the aggregator build for now, taking it out of the
general Maven build and remove it once Seam has upgraded to HV 4.x
Gunnar
2011/1/17 Emmanuel Bernard <emmanuel(a)hibernate.org>
On 17 janv. 2011, at 13:18, Hardy Ferentschik wrote:
> On Mon, 17 Jan 2011 13:06:07 +0100, Emmanuel Bernard <
emmanuel(a)hibernate.org> wrote:
>
>> 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.
>
> Ok. I would hope though that any new release would use Validator 4 :)
>
Probable, but unless you follow what they are doing, and remind them, there
is no guaranty :)
>
>> BTW how do you split a Git repo? simply by cloning and removing what you
don't want?
>
> That would be the easiest approach. But I think if you want to do it
properly
> you would have to use some git plumbing commands, eg filter-branch
>
True. That rewrites history though, right? Not sure it's something wanted.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev