Hi Gunnar,
I think we all agree that sometimes we can/should re-organize the
packages in a better structure - but as you suggest in major releases.
The problem is that deciding that "today I'm going to move all classes
to their right place" is unfortunately wishful thinking as you'll
never get it
Looks useful to update our integration tests, but I'm confused by the
versioning scheme:
http://maven.repository.redhat.com/earlyaccess/all/org/jboss/as/jboss-as-dist/7.4.0.Final-redhat-4/
TiA,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jb
On Thu, Aug 28, 2014 at 03:54:36PM +0100, Sanne Grinovero wrote:
> Looks useful to update our integration tests, but I'm confused by the
> versioning scheme:
>
> http://maven.repository.redhat.com/earlyaccess/all/org/jboss/as/jboss-as-dist/7.4.0.Final-redhat-4/
I guess the artifact is jboss-as-di
And again many thanks to Yoann Gendre for nailing a very subtle bug.
http://in.relation.to/Bloggers/YetAnotherJPA20CompatibleReleaseOfHibernateSearch
Regards,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mai
All, especially OGM team,
I guess Hardy already figured it out when reviewing my last pull
request: that artifact contains the latest JBoss EAP 6.3 version, very
convenient for integration tests.
Apparently the Maven artifact names still use the JBossAS naming and
version scheme, that's why it's
