[hibernate-dev] [validator] Time to let go

2011-01-17 Thread Hardy Ferentschik
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. hibe

Re: [hibernate-dev] [validator] Time to let go

2011-01-17 Thread Emmanuel Bernard
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, > >

Re: [hibernate-dev] [validator] Time to let go

2011-01-17 Thread Hardy Ferentschik
On Mon, 17 Jan 2011 13:06:07 +0100, Emmanuel Bernard 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 > BTW how do

Re: [hibernate-dev] [validator] Time to let go

2011-01-17 Thread Emmanuel Bernard
On 17 janv. 2011, at 13:18, Hardy Ferentschik wrote: > On Mon, 17 Jan 2011 13:06:07 +0100, Emmanuel Bernard > 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 hop

Re: [hibernate-dev] Clever dirty checking for Hibernate Search

2011-01-17 Thread Emmanuel Bernard
We can experiment with such approach but I am not sure that will work properly. Here are a couple of issues: - what about entities exposing data via fields - what if I poll data from an outside source and need that to be refreshed even if I do not change nor read the entity (there is one such e

Re: [hibernate-dev] Clever dirty checking for Hibernate Search

2011-01-17 Thread Sanne Grinovero
2011/1/17 Emmanuel Bernard : > We can experiment with such approach but I am not sure that will work > properly. Here are a couple of issues: Yes I just tossed the idea on the table, not sure either how far it can get, but if it worked it would be a pretty nice API. >  - what about entities expo

Re: [hibernate-dev] [validator] Time to let go

2011-01-17 Thread Gunnar Morling
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 aggreg