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.
-
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
steve.ebersole(a)jboss.com
steve.ebersole(a)redhat.com
On Mon, 2009-03-23 at 19:20 -0400, Emmanuel Bernard wrote:
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 moving these things back together
> was to make the compatibility "matrix" more manageable. Making
> incompatible changes in dependency common to core/annotations/em and
> search effectively makes those things incompatible as well. Same for
> integrating it into annotations.
Right but commons annotations should really be considered at the same
level as slf4j.
All Hibernate projects do share slf4j but Search and Validator are
independent of core (release wise and even to a certain extends at
runtime).