On Mar 25, 2009, at 15:55, Hardy Ferentschik wrote:
On Tue, 2009-03-24 at 21:51 -0400, Emmanuel Bernard wrote:
1) If commons-annotations *does not* rely on hibernate-core in any
way
then I'm fine to break it it back out if that makes sense.
However
y'all need to be *extremely* careful ab
On Tue, 2009-03-24 at 21:51 -0400, Emmanuel Bernard wrote:
> >>> 1) If commons-annotations *does not* rely on hibernate-core in any
> >>> way
> >>> then I'm fine to break it it back out if that makes sense. However
> >>> y'all need to be *extremely* careful about this and making sure
> >>> ab
By release series you mean 3.x or 3.1.x
In any case so far it has maintain such compatibility.
The trickiness here is that one particular feature of HSearch does
rely on a new feature of commons annotations and require that
annotations and entitymanager embrace this new feature to function
Sure, but by the same token I would not upgrade from sl4fj 1.5.x to
1.6.x (on the assumption that that introduces an incompatibility)
between hibernate 3.3.1 and 3.3.2.
The same needs to apply here. commons-annotations needs to maintain a
level of compatibility within a release series.
-
Ste
On Mar 23, 2009, at 09:31, Steve Ebersole wrote:
1) If commons-annotations *does not* rely on hibernate-core in any way
then I'm fine to break it it back out if that makes sense. However
y'all need to be *extremely* careful about this and making sure about
compatibility. The whole idea about
1) If commons-annotations *does not* rely on hibernate-core in any way
then I'm fine to break it it back out if that makes sense. However
y'all need to be *extremely* careful about this and making sure about
compatibility. The whole idea about moving these things back together
was to make the com
Hi there,
I would like to start a discussion around a few 'management' questions.
1. What shall we do with commons-annotations? commons-annotations became a
module of Core (core/trunk/commons-annotations) when we moved
Annotations
and EntityManager into Core. Emmanuel, raised the questio
