On 06/27/2016 11:44 AM, Sanne Grinovero wrote:
> On 27 June 2016 at 16:23, Scott Marlow wrote:
>>>
>>> That dependency to org.hibernate:main from org.jboss.as.ejb3 still looks
>>> a bit scary. My simple test passes, not sure whether that may be a
>>> problem in other cases, though?
>>>
>>
>> Sor
On 27 June 2016 at 16:23, Scott Marlow wrote:
>>
>> That dependency to org.hibernate:main from org.jboss.as.ejb3 still looks
>> a bit scary. My simple test passes, not sure whether that may be a
>> problem in other cases, though?
>>
>
> Sorry, I missed this part of your email. EJB3 timers are usi
>
> That dependency to org.hibernate:main from org.jboss.as.ejb3 still looks
> a bit scary. My simple test passes, not sure whether that may be a
> problem in other cases, though?
>
Sorry, I missed this part of your email. EJB3 timers are using
Hibernate [1].
Scott
[1]
https://github.com/wild
On 27 June 2016 at 15:00, Gunnar Morling wrote:
> Hey,
>
> I've sent PR https://github.com/hibernate/hibernate-orm/pull/1455 earlier
> today for this.
>
>> What happens if we copy the contents of the
>> org.hibernate.jipijapa-hibernate5 module, to
>> org.hibernate.jipijapa-hibernate5-1.
>> Change
Hey,
I've sent PR https://github.com/hibernate/hibernate-orm/pull/1455 earlier
today for this.
> What happens if we copy the contents of the org.hibernate.jipijapa-hibernate5
module, to org.hibernate.jipijapa-hibernate5-1.
> Change org.hibernate.jipijapa-hibernate5-1, to depend on ORM 5.1 and
cha
On 06/25/2016 05:12 PM, Sanne Grinovero wrote:
> On 25 June 2016 at 13:15, Gunnar Morling wrote:
>> Ok, so this was caused by the module dependency
>> from org.hibernate.jipijapa-hibernate5 to org.hibernate. Seems I need to
>> create a 5.1-specific adapter module, too, and require that to be
>>
On 25 June 2016 at 13:15, Gunnar Morling wrote:
> Ok, so this was caused by the module dependency
> from org.hibernate.jipijapa-hibernate5 to org.hibernate. Seems I need to
> create a 5.1-specific adapter module, too, and require that to be
> configured by users via jboss.as.jpa.adapterModule.
If
Ok, so this was caused by the module dependency
from org.hibernate.jipijapa-hibernate5 to org.hibernate. Seems I need to
create a 5.1-specific adapter module, too, and require that to be
configured by users via jboss.as.jpa.adapterModule.
2016-06-25 11:53 GMT+02:00 Gunnar Morling :
> Scott, all,
Scott, all,
As discussed I've started to work on a module ZIP which can be used to add
Hibernate ORM 5.1 to an existing WildFly 10.0 instance (which comes with
ORM 5.0). As module slot I'm using "5.1".
Now I assumed that it'd be enough to set this property in persistence.xml:
jboss.as.jpa.p
On 8 June 2016 at 16:08, Gunnar Morling wrote:
> It'd not only be a library, but an image containing WF with the latest
> Hibernate ORM. But as said, the module ZIP is more versatile and is what I'd
> do.
+1 for the priority on ZIP files.
I had not understood that you meant to re-distribute a cu
It'd not only be a library, but an image containing WF with the latest
Hibernate ORM. But as said, the module ZIP is more versatile and is what
I'd do.
2016-06-08 16:59 GMT+02:00 Sanne Grinovero :
> On 8 June 2016 at 08:11, Gunnar Morling wrote:
> > 2016-06-07 15:51 GMT+02:00 Steve Ebersole :
>
I don't know. I was just thinking of distribution. I really know very
little about WF modules
On Wed, Jun 8, 2016 at 9:59 AM Sanne Grinovero wrote:
> On 8 June 2016 at 08:11, Gunnar Morling wrote:
> > 2016-06-07 15:51 GMT+02:00 Steve Ebersole :
> >
> >> Too bad we can't just publish a Docker i
On 8 June 2016 at 08:11, Gunnar Morling wrote:
> 2016-06-07 15:51 GMT+02:00 Steve Ebersole :
>
>> Too bad we can't just publish a Docker image.
>>
>
> We could do that, but I think we should have a solution for non-Docker
> users, too.
What's the point to package a library in a Docker image?
>
>
2016-06-07 15:51 GMT+02:00 Steve Ebersole :
> Too bad we can't just publish a Docker image.
>
We could do that, but I think we should have a solution for non-Docker
users, too.
>
> Is this something we'd publish somewhere (Nexus/Artifactory)?
>
Yes, we'd publish it in Nexus and also BinTray/Sou
Too bad we can't just publish a Docker image.
Is this something we'd publish somewhere (Nexus/Artifactory)? I know
nothing about building a WF module ZIP. But if you are willing to do the
work and it helps OGM etc, of course we would incorporate it.
On Tue, Jun 7, 2016 at 8:19 AM Gunnar Morling
Hi,
As discussed by some of us during the No ORM meeting in May, it'd be great
if there was a module ZIP allowing people to easily upgrade Hibernate ORM
in the WildFly version they are using.
Just the other day there was a blog post published [1] describing how to
use Hibernate ORM 5.2 in WF 10,
16 matches
Mail list logo
