On Fri, Jan 19, 2018 at 5:33 PM, Steve Ebersole wrote:
> yessir
>
Nice, thanks for confirming.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
yessir
On Fri, Jan 19, 2018 at 10:28 AM Guillaume Smet
wrote:
> On Fri, Jan 19, 2018 at 5:15 PM, Steve Ebersole
> wrote:
>
>> Agreed. So unless someone has an argument against, I will plan on
>> switching over to Bintray publishing for the next 5.3 release.
>>
>
> Not an argument against but j
On Fri, Jan 19, 2018 at 5:15 PM, Steve Ebersole wrote:
> Agreed. So unless someone has an argument against, I will plan on
> switching over to Bintray publishing for the next 5.3 release.
>
Not an argument against but just to be sure, you will be able to
synchronize artifacts from the org.hiber
Agreed. So unless someone has an argument against, I will plan on
switching over to Bintray publishing for the next 5.3 release.
This means we will need to update the older versions we still want to
release to publish to Bintray. Gail, that's just which versions?
On Fri, Jan 19, 2018 at 9:35 A
Awesome, congratulations all!
On 19 January 2018 at 15:33, Steve Ebersole wrote:
> http://in.relation.to/2018/01/18/hibernate-orm-530-beta1-release/
> ___
> hibernate-announce mailing list
> hibernate-annou...@lists.jboss.org
> https://lists.jboss.org/m
On 19 January 2018 at 14:56, Steve Ebersole wrote:
> I think it is reasonable to only publish the maven artifacts to Bintray and
> continue to publish the bundles to SourceForge.
Great, so that means we can have about a thousand releases on Bintray;
should be enough for all our projects for at le
http://in.relation.to/2018/01/18/hibernate-orm-530-beta1-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Yes. The enhancing is done based on the underlying BytcodeProvider's
Enhancer. However knowing what classes to enhance is driven by Hibernate's
boot-time model. Building this boot-time model requires access to
DatabaseMetaData.
On Fri, Jan 19, 2018 at 7:41 AM Scott Marlow wrote:
> > One WildF
I think it is reasonable to only publish the maven artifacts to Bintray and
continue to publish the bundles to SourceForge.
On Fri, Jan 19, 2018 at 7:19 AM Sanne Grinovero wrote:
> On 19 January 2018 at 13:05, Steve Ebersole wrote:
> > I sat down and did some calculations to get a better idea
> One WildFly issue is that the application datasources aren't available
> until late in WildFly deployment but the JPA container needs to register
> the JPA classloader level transformers very early, so Hibernate can rewrite
> application classes. This is further complicated by our WildFly CDI
>
On 19 January 2018 at 13:05, Steve Ebersole wrote:
> I sat down and did some calculations to get a better idea of whether this is
> feasible. 5.3.0.Beta1 had a total size of 135M (31M in "maven artifacts",
> 104 in release bundles). At 30G limit, we'd be able to do ~222 releases
> before we hit
I sat down and did some calculations to get a better idea of whether this
is feasible. 5.3.0.Beta1 had a total size of 135M (31M in "maven
artifacts", 104 in release bundles). At 30G limit, we'd be able to do ~222
releases before we hit that limit (30 / .135 = 222.)
So if only ORM is going t
Hi Steve,
As for ORM, you also need to add a per version Documentation page as they
are specific per version (this is preexisting to the changes we made with
Yoann, that's why I didn't mention it in my email):
https://github.com/hibernate/hibernate.org/tree/staging/orm/documentation
In passing, I
13 matches
Mail list logo
