I'm going to use org.hibernate.Version.getVersionString() to detect a
Hibernate 3.x provider versus 4.x.
This is currently [WORKING] in 4.0.0.Beta4/Beta5. Would be good to have
it correct for the next 4.x build.
On 07/18/2011 04:39 AM, Emmanuel Bernard wrote:
> You can use org.hibernate.Versio
You can use org.hibernate.Version.getVersionString()
which is the version number + qualifier OR [WORKING] when a snapshot is used.
Emmanuel
On 16 juil. 2011, at 19:56, Scott Marlow wrote:
> It doesn't cause me great pain to not have this, would just make a few
> AS integration tasks simpler (wh
I agree with Steve.
On 16 juil. 2011, at 19:07, Steve Ebersole wrote:
> I am personally against this idea. You mention renaming one single
> class, but in reality we would need different FQNs for each and every
> class otherwise we run into a clash in the class loader as to which one
> wins (
It doesn't cause me great pain to not have this, would just make a few
AS integration tasks simpler (when dealing with multiple versions of
Hibernate).
I understand that there are more environments than just AS. For AS7, it
was more because I am using the persistence provider class name as a k
I am personally against this idea. You mention renaming one single
class, but in reality we would need different FQNs for each and every
class otherwise we run into a clash in the class loader as to which one
wins (the one from hibernate4 jar or the one from hibernate3 jar).
This is a bad path
If someone wanted to include both Hibernate 3 + Hibernate 4 in the same
project, that might be easier if the Hibernate 4 artifacts had a version
number in it or was changed for every new major release. I don't think
Maven supports building two versions of the same artifact (at the same
depende
