Re: [hibernate-dev] OSGI manifests for hibernate-orm

2012-08-15 Thread Steve Ebersole
Ever hit send and immediately know you wanted to stop it/take it back ;) https://hibernate.onjira.com/browse/HHH-7527 On Wed 15 Aug 2012 07:39:29 PM CDT, Steve Ebersole wrote: > Martin, Brett, > > I went ahead and created a Jira for this. Lets discuss there. > > On Wed 15 Aug 2012 07:30:51 PM C

Re: [hibernate-dev] OSGI manifests for hibernate-orm

2012-08-15 Thread Steve Ebersole
Martin, Brett, I went ahead and created a Jira for this. Lets discuss there. On Wed 15 Aug 2012 07:30:51 PM CDT, Brett Meyer wrote: > > Martin makes good points. I'd highly recommend moving this into JIRA. > As frequently as Hibernate gets used within OSGi contexts, following > some basic guidel

Re: [hibernate-dev] OSGI manifests for hibernate-orm

2012-08-15 Thread Brett Meyer
Martin makes good points. I'd highly recommend moving this into JIRA. As frequently as Hibernate gets used within OSGi contexts, following some basic guidelines would be incredibly helpful. +1 for enforcing package splits, as well as ensuring the manifests are generated correctly/automaticall

Re: [hibernate-dev] OSGI manifests for hibernate-orm

2012-08-15 Thread Steve Ebersole
Martin, Totally agree about the org.hibernate.engine.spi bits. Thats always been fugly hack. Both org.hibernate.engine.spi.CascadeStyle and org.hibernate.engine.spi.CascadingAction attempt to combine contracts and enumerations, which I have never been a fan of here. I think its fine when tha

[hibernate-dev] OSGI manifests for hibernate-orm

2012-08-15 Thread mail...@bibbernet.org
Hello, because I need clean OSGI bundles for Hibernate and especially Envers, I am working on some patches for the 4.1 branch of hibernate-orm to enable generation of OSGI compatible jar files. During the work I have found the following problems, and need some help and/or feedback. The probl

Re: [hibernate-dev] org.hibernate.jpa.test.packaging.PackagingTestCase

2012-08-15 Thread Steve Ebersole
Forgot to mention, the reason I am asking is that the current set up makes it more difficult to test in IDE. If you change one of these src/test/bundles files, you have to switch to command line, run gradle compilation (because it is a custom gradle task that copies the files over) before I ca

[hibernate-dev] org.hibernate.jpa.test.packaging.PackagingTestCase

2012-08-15 Thread Steve Ebersole
org.hibernate.jpa.test.packaging.PackagingTestCase uses ShrinkWrap to facilitate "packaged" JPA tests. It uses metadata from src/test/bundles, BUT it gets the copies moved over to target/bundles. I am curious why it uses the target/bundles copy rather than the src/test/bundles original? --