Currently Bintray is not automatically publishing to Central. I'm not sure
why yet. But it's easy to manually sync after.
I can walk you through that if you need.
Other than that, it usually goes pretty smoothly
On Wed, May 23, 2018, 5:37 PM Chris Cranford wrote:
> I
I already mentioned to Sanne I'd handle it.
I might run into some publishing issues and might need to recruit some
help as needed since it'll be my first attempt, but we'll see.
Chris
On 05/23/2018 06:25 PM, Sanne Grinovero wrote:
> we'll draft a "volunteer" :)
>
> Thanks!
>
> On 23 May 2018
If someone can do the release, +1 from me
On Wed, May 23, 2018 at 5:11 PM Sanne Grinovero wrote:
> Hi Steve,
>
> are we free to release a 5.3.1 this weekend?
>
> As I mentioned in the parallel thread "WildFly 14 requirements for
> Hibernate libraries", we can still get some
Hi Steve,
are we free to release a 5.3.1 this weekend?
As I mentioned in the parallel thread "WildFly 14 requirements for
Hibernate libraries", we can still get some fixes for WildFly 13 but
the deadline is this weekend.
I think you and Andrea can keep the focus on the ORM6 meeting;
everyone
Andrea and I have spent some time getting the SQL execution design doc
up-to-date. Would be nice to get any feedback. Thanks :)
https://github.com/sebersole/hibernate-core/blob/wip/6.0-merge/sql-engine-design.adoc
___
hibernate-dev mailing list
Execution of procedure calls, function calls and anonymous blocks can all
lead to JDBC returning us multiple ResultSets.
To account for this (for the first 2 anyway) JPA allows defining multiple
ResultSetMapping references for the StoredProcesdureQuery. Alternatively,
it allows specifying
By "read only" I assume you mean immutable (aka,
Collections#immutableMap)? If so, sure, that is a decent solution...
On Wed, May 23, 2018 at 7:55 AM Scott Marlow wrote:
> For the WildFly use of ServiceContributor [1], which registers for each
> SF/EMF, the 2lc
For the WildFly use of ServiceContributor [1], which registers for each
SF/EMF, the 2lc RegionFactoryInitiator + JtaPlatform, I am worried that
we don't yet have a "per app deployment" way to disable the WF
ServiceContributorImpl.
I'm thinking that some applications (e.g. Spring) may not want