Re: [hibernate-dev] Does Hibernate ORM bytecode enhance application entity classes by default?

Hi Scott, I can only comment on the initial question. No, hibernate does not automatically enhance entities. Entities are either enhanced at build time or after WildFly has pushed the right ClassTransformer (based on "hibernate.enhance.*" properties in persistence.xml). I'm not aware of any

Re: [hibernate-dev] replace Pax Exam with Docker

One of them there build tool profile or switch thingies.  Sorry, been in Maven land for too long these days... On 1/18/18 5:21 PM, Steve Ebersole wrote: > > I'm ok with it.  But we use Gradle, so it'll be hard to use a Maven > profile ;) > > > On Thu, Jan 18, 2018, 4:14 PM Brett Meyer

Re: [hibernate-dev] replace Pax Exam with Docker

I'm ok with it. But we use Gradle, so it'll be hard to use a Maven profile ;) On Thu, Jan 18, 2018, 4:14 PM Brett Meyer wrote: > Thanks Chris! Steve, not sure if you officially voted -- any concerns? > Andrea? Anyone else? > > Again, this would all be disabled by

Re: [hibernate-dev] replace Pax Exam with Docker

Thanks Chris!  Steve, not sure if you officially voted -- any concerns?  Andrea?  Anyone else? Again, this would all be disabled by default, behind a Maven profile... On 1/16/18 3:15 PM, Chris Cranford wrote: > On 01/12/2018 12:54 PM, Sanne Grinovero wrote: >> On 12 January 2018 at 17:32,

[hibernate-dev] Does Hibernate ORM bytecode enhance application entity classes by default?

Hi, Did we change Hibernate to automatically enhance/rewrite application entity classes by default? I remember hearing a few times that we would but don't remember if that happened. This is related to WildFly jira WFLY-8858 [1], which I'm not yet sure of how to completely fix (involves deal

Re: [hibernate-dev] HHH-12172 - Bintray v. OSSRH

Bintray said they would increase the storage limit to 30G for Hibernate. However that limit is per organization, which is the top-level thing ( https://bintray.com/hibernate). I think we'd eat that up in no time, especially if other projects plan on moving to Bintray at any time. One way around

Re: [hibernate-dev] staging.hibernate.org CI failure

That did help, thanks! One additional step is to add `hibernate.org/orm/releases/5.3/index.adoc` too I am capturing all of this on our release steps wiki On Thu, Jan 18, 2018 at 12:43 PM Guillaume Smet wrote: > See the thread "ORM release process" I started in late

Re: [hibernate-dev] staging.hibernate.org CI failure

Yes, I had seen that. We definitely need a bunch of notes in the release process about all these new steps On Thu, Jan 18, 2018 at 12:38 PM Guillaume Smet wrote: > Hi Steve, > > I have to go very soon so I can't test myself right now but that might be > because you're

Re: [hibernate-dev] staging.hibernate.org CI failure

See the thread "ORM release process" I started in late September. HTH. On Thu, Jan 18, 2018 at 7:40 PM, Steve Ebersole wrote: > Yes, I had seen that. > > We definitely need a bunch of notes in the release process about all these > new steps > > On Thu, Jan 18, 2018 at

Re: [hibernate-dev] staging.hibernate.org CI failure

Hi Steve, I have to go very soon so I can't test myself right now but that might be because you're missing this file in the 5.3 directory: https://github.com/hibernate/hibernate.org/blob/d22b1461ee5ae7aac56cff90e4869b57599bb321/_data/projects/orm/releases/5.2/series.yml You need one to describe

[hibernate-dev] staging.hibernate.org CI failure

I am trying to finish up the announce and website changes for 5.3.0.Beta1. staging.in.relation.to changes built fine. However I am getting incomprehensible (to me) failures on the CI server trying to build the staging website. Help? ___ hibernate-dev

Re: [hibernate-dev] 5.3.0.Beta1 delay

As far as I know they just require some useful information: license, developers, description and a url. Isn't it easier to just add these? In case of the relocations we have in Hibernate Search, I just declare a description and then declare the parent pom so that most other things are inherited.