Hi Rory,
many thanks, we'll start testing this soon.
Sanne
On Tue, 12 Nov 2019 at 10:08, Rory O'Donnell wrote:
>
> Hi Sanne,
>
> *OpenJDK builds - JDK 14 *- Early Access build 22 is available at
> http://jdk.java.net/14/
>
> These early-access, open-source builds are provided under the GNU
>
Congratulations for this huge milestone!
On Tue, 24 Sep 2019 at 08:15, Yoann Rodiere wrote:
>
> Hello,
>
> Hibernate Search 6 just reached Beta status with the release of version
> 6.0.0.Beta1.
>
> This release clears the last remaining major hurdles: it fixes the few
> remaining inconsistencies
Hi Rory,
many thanks for the news!
All our projects are working fine on JDK13 - provided of course people
update to latest releases.
Also called it out explicitly yesterday just after the release:
- https://in.relation.to/2019/09/17/hibernate-orm-5-4-5-Final/
Thanks,
Sanne
On Tue, 17 Sep 2019
Hello all,
we've released Hibernate ORM version 5.4.5.Final !
It's just a micro, but contains several interesting improvements.
Please have a look at the release post:
- https://in.relation.to/2019/09/17/hibernate-orm-5-4-5-Final/
And maybe help spreading the news?
-
I've completed a rebase of Steve's latest ORM6 branch onto our latest ORM5
master, so to have it incorporate all latest bugfixes and performance
enhancements we recently developed on master.
To be more specific, this is a rebase of commit 'wip/sqm-jpa-types-sql-ast'
[2e002c73c6] onto 'master'
OK to change JdbcObserverImpl#observers from a
>> List, to:
>>
>> private final transient ConnectionObserver observer;
>>
>> Also, I'm fine with ConnectionObserver being deprecated, and later removed.
>>
>> Steve, WDYT?
>>
>>
>> On Tue, Aug 20,
While refactoring some related optimisations, I noticed there's
currently no way to register a custom ConnectionObserver.
There seems to be only one implementation, which is registered by default:
-
org.hibernate.internal.ConnectionObserverStatsBridge#ConnectionObserverStatsBridge
Some
stry().
>
> My preference is to follow our normal process for removing an SPI.
>
> In general, we try not to remove SPIs within a minor release (e.g., 7.x). We
> normally deprecate the method in 7.x. The soonest we would remove it would be
> in 7.x+1.
>
> Regards,
Hi all,
is this method needed?
- org.hibernate.resource.jdbc.ResourceRegistry#cancelLastQuery
It seems undocumented, untested, and everything compiles just fine if
I just delete it - however it seems marked as API.
But also, I suppose this should be invoked by a different thread as
the one
Hi Rory,
glad to report that all our projects seem to be able to complete their
respective testsuite on OpenJDK 13 build 33: no regressions found so
far!
Thanks and regards,
Sanne
On Sat, 10 Aug 2019 at 11:29, Rory O'Donnell wrote:
>
> Hi Sanne,
>
>
> Haven't heard from you in some time, any
Cool, thanks!
I think we're good now, we'll just go with it. Worst case it's easy to revert.
On Wed, 7 Aug 2019 at 14:44, Scott Marlow wrote:
>
> Hi Sanne,
>
> WildFly doesn't reference StatisticsImpl, WildFly does use Statistics.
>
> Scott
___
n Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
>
> On Wed, 7 Aug 2019 at 11:08, Sanne Grinovero wrote:
>>
>> Hi all,
>>
>> while working on HHH-13527 I noticed that there's quite some
>> complexity in StatisticsImpl to deal with the f
Hey all,
we've been working on various performance optimisations for Hibernate
ORM; some were large and complex, some others where very small little
things.
I've been measuring impact step by step so far; quite happy to see the
"combined" results are better than what I was hoping:
Hibernate ORM
On Tue, 18 Jun 2019 at 14:19, Mark Rotteveel wrote:
>
> On 16-6-2019 16:28, Mark Rotteveel wrote:
> > After a significant hiatus, I have restarted my work on adding improved
> > support for Firebird 2.5 and 3.0 (and more importantly struggling
> > through some test failures).
> >
> > I am
of us spending more QA love on
them, but because they implicitly mark a time in which we can finally drop
compatibility with older stuff, and benefit from cool new stuff.
> --Gunnar
>
>
>
> Am Mo., 17. Juni 2019 um 10:44 Uhr schrieb Sanne Grinovero <
> sa...@hibernate.org>:
>
On Mon, 17 Jun 2019 at 08:17, Yoann Rodiere wrote:
>
> Hello team,
>
> Following the notification above, I updated CI to use the latest JDK13.
>
> I also configured JDK14 so you can use in your builds. It's named,
> unsurprisingly, "OpenJDK 14 Latest". Please set up Jenkins jobs as
> appropriate
Hey all,
today I'll be restarting the server running ci.hibernate.org, and
installing some updates.
You can login as usual, but it might ask your permission again to
allow github to share your profile with the ci server.
I will need to repeat such operation multiple times this week, please
be
It wasn't moved yet.
On Thu, 23 May 2019 at 10:20, Gunnar Morling wrote:
>
> Hi all,
>
> Just tried to reach in.relation.to via HTTPS, but it doesn't connect. Has
> it not been moved to HTTPS yet, or is something broken there?
>
> --Gunnar
> ___
>
Hi Gail,
I'm familiar with the Gradle plugin portal, happy to look into this.
Thanks for highlighting this one!
I'll be off for travelling and conferences the next two weeks. If
anyone needs this earlier, feel free to take the issue but le me know
:)
Thanks,
Sanne
On Tue, 9 Apr 2019 at 04:36,
On Tue, 26 Mar 2019 at 15:08, Steve Ebersole wrote:
>
> On Tue, Mar 26, 2019 at 9:57 AM Sanne Grinovero wrote:
>>
>> One question: could we benefit from "cascade delete" rules defined in
>> the table structure?
>>
>>
>> If Hibernate ORM was abl
Hi Steve,
this does sound amazing, I think it's certainly worth trying to have
the most efficient strategy chosen on a per-entity base.
One question: could we benefit from "cascade delete" rules defined in
the table structure?
If Hibernate ORM was able parse the cascading rules from existing
> > expect micros to be drop-in replacements, and I can imagine adding/removing
> > dependencies to cause trouble in build tools/build configuration.
> > But I wouldn't make it a hard rule, either: we may be forced to do it one
> > day because of a bug, and such a sma
Hi Rory,
we've tested JDK 12 build 32 and it's working fine for Hibernate ORM;
some more Hibernate projects are being tested soon - we'll let you
know.
While testing for this, we've hit an annoying build problem with
Javadoc though; I've commented here:
-
Hi all,
I just tested if we still need the dependency to
'javax.activation:javax.activation-api:1.2.0' from Hibernate ORM /
master, as I was suspecting the original reasons to add it might be
out of date.
I guessed almost right, as it turns out we don't need this dependency
for Java 11, nor it
great! Thanks Guillaume
On Sat, 19 Jan 2019 at 19:27, Guillaume Smet wrote:
>
> The release is done.
>
> I'll announce it on Monday.
>
> On Sat, Jan 19, 2019 at 6:47 PM Guillaume Smet
> wrote:
>
> > Hi,
> >
> > I'm in the process of releasing 5.4.1.Final, please don't push anything to
> >
ve
> > to make it at some point. So if you want something else, I'd be happy to
> > hear about that :)
> >
> > Yoann Rodière
> > Hibernate NoORM Team
> > yo...@hibernate.org
> >
> >
> > On Thu, 6 Dec 2018 at 16:16, Steve Ebersole wrote:
> >
> &
ERROR. Some of the more recent changes by Guillaume change that a
> bit and moved a few message logger messages to be DEBUG. I think this is
> another thing we should nail down moving forward - do we want TRACE/DEBUG
> logging to potentially be messaged (with id) logs?
>
>
>
" in the code.
>
> So I think we are covered here.
Nice, thanks for checking.
>
> --
> Guillaume
>
> On Fri, Jan 11, 2019 at 12:04 PM Sanne Grinovero wrote:
>>
>> On Fri, 11 Jan 2019 at 09:53, Guillaume Smet
>> wrote:
>> >
>> > So what
Hi all,
I plan to tag a maintenance release of Hibernate ORM 5.4.1.Final on
Thursday, to be published and distributed Friday.
Please try to polish and merge any work you might want included, or
yell at me if you object with the timing?
And of course, as usual:
don't freak out if your work won't
On Fri, 11 Jan 2019 at 14:00, Steve Ebersole wrote:
>
> Guillaume - I added a general start-a-discussion comment to the PR.
> Hopefully anyone with an opinion on that can chime in there. Beyond that, +1
>
>
> Sanne - ok, I see. You are not expecting users to have to deal with
>
we could agree on quickly:
>> https://github.com/hibernate/hibernate-orm/pull/2728
>>
>> --
>> Guillaume
>>
>> On Thu, Jan 10, 2019 at 5:38 PM Steve Ebersole wrote:
>>>
>>>
>>>
>>> On Thu, Jan 10, 2019 at 10:15 AM Sanne Grinovero
On Thu, 10 Jan 2019 at 16:39, Steve Ebersole wrote:
>
>
>
> On Thu, Jan 10, 2019 at 10:15 AM Sanne Grinovero wrote:
>>
>> On Thu, 10 Jan 2019 at 01:44, Steve Ebersole wrote:
>> >
>> > I disagree that logging a single message is a better solution be
enhanced classes,
>> hibernate.properties missing and a few others) but keep the important
>> diagnostic information as is.
>>
>> On Wed, Jan 9, 2019 at 2:23 PM Sanne Grinovero wrote:
>>
>> > +1 to polish output, but:
>> >
>> > I don't want t
+1 to polish output, but:
I don't want to need to figure out how to reconfigure whatever Logger
of the day one happens to hit, to finally notice that essential
configuration details are wrong. Mostly because it requires to get the
idea to actually check this, which is not a straightforward
Congratulations !!
On Fri, 7 Dec 2018 at 12:31, Steve Ebersole wrote:
>
> We have released the first Alpha for ORM version 6.0 -
> http://in.relation.to/2018/12/06/hibernate-orm-600-alpha1-out/
> ___
> hibernate-announce mailing list
>
ly checking the user rooms once in a
> >> while
> >> >>> (might work if Gitter sends emails when your are mentioned while
> >> offline).
> >> >>> So, yeah, in short: I don't really know.
> >> >>>
> >> >>> > More jus
On Thu, 6 Dec 2018 at 13:17, Guillaume Smet wrote:
>
> Hi Steve,
>
> I don't particularly like it.
>
> We have very few resources to work on 5.x and clearly we won't be able to
> do that + learn about 6 in parallel and fix issues in both, probably in 2
> completely different ways. And we won't
On Wed, 5 Dec 2018 at 20:10, Steve Ebersole wrote:
>
> Another one..
>
> `hibernate-orm-modules` defines a `hibernate-envers` module (in the WF
> modules sense). Since envers is now part of `hibernate-core` should we
> remove that module or have it just act as an alias for the main orm module?
On Wed, 5 Dec 2018 at 13:56, Steve Ebersole wrote:
>
> As I am preparing the Alpha1 release a few topics of discussion have come
> up...
>
> Previously (last year's f2f) we had decided to unify the artifact naming
> conventions; specifically for ORM this meant renaming the groupId from
>
Hi all,
I reconfigured some details of Mailman regarding this list, following
advice from Red Hat sysadmins. This is unlikely to solve the problems
but should help us get some diagnostic data which is sadly missing at
this moment.
Please do not make any change, or reach out to me in case of such
tions are the only way we can get notified of comments on our
>> > posts...
>> >
>> >
>> > Yoann Rodière
>> > Hibernate NoORM Team
>> > yo...@hibernate.org
>> >
>> >
>> > On Thu, 15 Nov 2018 at 13:37, Sanne Grinovero w
Awesome, congratulations all!
On Thu, 15 Nov 2018 at 15:30, Guillaume Smet
wrote:
>
> Hi,
>
> We just released Hibernate ORM 5.4.0.CR1, the first candidate release of
> 5.4.0.
>
> 5.4 is the direct continuation of 5.3 and we will encourage everyone to
> upgrade to it to benefit from the latest
Apparently I stopped receiving notifications from Discus about needing
to approve a comment, and it looks like you all did?
I just noticed as someome mentioned "while my other comment is not
approved" and I thought "wait, what? I know nothing about other
pending comments.." and didn't see any
This was now resolved by Atlassian support. Thanks all!
On Fri, 2 Nov 2018 at 10:46, Sanne Grinovero wrote:
>
> Hi all,
>
> I'm receiving requests to approve people who are creating accounts on JIRA.
>
> While it's good to see lots of people interested in registering, I've
>
ernate-dev on IRC requiring an account).
Assuming the new chat platform takes off, there's a risk it might be
too successful as well. But I guess we'll see, or let's use a very
bad chat platform so to keep people from coming :P
>
>
> Yoann Rodière
> Hibernate NoORM Team
>
n created some more rooms recently.
Should we enforce people to have a Github account? I'd like that, I
think it would better nudge towards getting the right type of people
to join.
Thanks,
Sanne
>
> On Mon, Nov 12, 2018 at 6:17 AM Guillaume Smet
> wrote:
>>
>> On Mon,
quot;URL Source" to "Credentials Store"
> > >> > > - In the "URL" box, select the entry corresponding to your
> > room,
> > >> > > which should normally appear as "Gitter webhook URL for the
> > > >> &
Hi Alvaro,
I forced the system to send you an HipChat invite. I don't know if it
works, good luck :)
You're very welcome to join us on gitter or IRC until we get clarity
on what we'll be using in the future.
Thanks,
Sanne
On Mon, 12 Nov 2018 at 14:48, Guillaume Smet wrote:
>
> Ah yes, I seem
an find solutions to some of the
> > > problems.
> > >
> > > I'll look into moving the Hibernate Search chat to Gitter and will report
> > > back on this thread.
> > >
> > > Yoann Rodière
> > > Hibernate NoORM Team
> > > yo...@hibe
see
>> what I may I have missed, which is quite frustrating.
>>
>> Chris
>>
>> On 10/24/18 9:26 AM, Alessio Stalla wrote:
>> > Hi,
>> > I've got the excessive bounces message several times, too, and I'm using
>> > Gmail.
>> >
>
Hi all,
I'm receiving requests to approve people who are creating accounts on JIRA.
While it's good to see lots of people interested in registering, I've
never had to approve these before.
Did someone change settings or should I report this to Atlassian?
Thanks,
Sanne
Awesome list of improvements. Congratulations all, gret release!
On Tue, 30 Oct 2018 at 11:52, Davide D'Alto wrote:
>
> Hibernate OGM 5.4.0.Final has been released!
>
> Here's some of the new features included in this release:
>
> - Infinispan remote transactions over HotRod client
> - JPQL and
> Gmail.
>
> Alessio
>
> On Wed, 24 Oct 2018 at 15:24, Sanne Grinovero wrote:
>>
>> Hi Jordan,
>>
>> I have an error message from our mail server stating that messages to
>> you (and 8 more people, among them we also have regulars like Vlad and
>> C
Hi Graham,
many thanks for your help!
Sorry for the lack of feedback on your PR, I'll remind the Tools
maintainer; looks like he might have missed the notification.
Thanks,
Sanne
On Tue, 23 Oct 2018 at 21:57, Graham Collinson
wrote:
>
> Apologies for the empty email last time
>
>
Hi Jordan,
I have an error message from our mail server stating that messages to
you (and 8 more people, among them we also have regulars like Vlad and
Christian Beikov) have been bouncing back often in the past 2 days. It
eventually gave up so you might miss some emails from this list.
I'm not
Thanks for starting this!
The choice of IRC is a bit special on the list as we never intended it
to be killed: it has been historically important and we should
maintain some level of reachability on it. So voting for the "IRC"
choice just means a preference to not use anything else on top of it,
Hi all,
github had some problems last night / this morning with their storage service.
Problem should have been solved by now, but social media highlithed
some reports of people having some of the most recent commits; in some
cases pull requests.
Nothing to panic about as git is well
On Mon, 22 Oct 2018 at 09:53, Guillaume Smet wrote:
>
> On Sun, Oct 21, 2018 at 9:48 PM Sanne Grinovero wrote:
>>
>> > I think it goes without saying but we still need to have ORM working
>> > without enhancement, considering how many bugs we have related to e
On Thu, 18 Oct 2018 at 14:02, Guillaume Smet wrote:
>
> Hi,
>
> On Thu, Oct 18, 2018 at 1:33 PM Sanne Grinovero wrote:
>>
>> > Regarding "BasicProxyFactory", Guillaume and I had to fight with this
>> > think a few weeks ago, I think. If I rem
On Thu, 18 Oct 2018 at 12:29, Steve Ebersole wrote:
>
> For me its ok. We end up handling each of these specifically anyway nowadays.
Thanks! I'll merge then.
>
> On Thu, Oct 18, 2018 at 6:16 AM Sanne Grinovero wrote:
>>
>> Since this is a rather un-interesting topic I
permissions that a user could edit their own comments.
> I think admins could edit any, but I do not remember that part for sure.
>
> On Thu, Oct 18, 2018 at 5:17 AM Sanne Grinovero wrote:
>>
>>
>> I can't remember ever being allowed to edit comments.
>>
>> For
asses.
>
>
> Yoann Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
>
> On Wed, 17 Oct 2018 at 19:47, Sanne Grinovero wrote:
>>
>> After some experimentation I figured out that the BytecodeProvider is
>> not really necessary, if you are happy t
Since this is a rather un-interesting topic I guess I'll just proceed with a PR:
- https://github.com/hibernate/hibernate-orm/pull/2594
It can easily be reverted in case someone badly wants it back.
On Wed, 17 Oct 2018 at 16:26, Sanne Grinovero wrote:
>
> Currently this method i
I can't remember ever being allowed to edit comments.
For sure it wasn't allowed years back, I don't honestly know about recent
times as I never tried - probably having been coached by the old rule :)
On Thu, 18 Oct 2018, 11:06 Steve Ebersole, wrote:
> Did someone remove the ability to edit
After some experimentation I figured out that the BytecodeProvider is
not really necessary, if you are happy to use the tools we have to
enhance the entities upfront.
In some environments such as on GraalVM I need to pre-enhance the
entities (need as in "not optional"), but some further things
Currently this method is used but not doing much at all, as maps
OBSOLETE_PROPERTIES and RENAMED_PROPERTIES are constant and empty.
I'm wondering if this is because it's just a coincidence at this point
in time we have nothing registered in those maps, or if this strategy
is just no longer the
Hi all,
I tagged a 5.0.5.Final release for the sole purpose of aligning the
dependency of org.jboss.logging:jboss-logging with version 3.3.2.Final
: no other changes.
Next I'll upgrade ORM as I need this; I guess upgrading other projects
is entirely optional as there's no real benefit - except
points out, storing epoch-based dates (Instant, etc) is always the
>> best option
>>
>> One cool option would be an AttributeConverter that handles the timezone
>> transformation, combined with telling Hibernate to always use UTC for the
>> JDBC timezone
>>
>
On Fri, 5 Oct 2018 at 10:28, Vlad Mihalcea wrote:
>
> Hi
>
> IMO no timezone conversion whatsoever should be applied when
> > persisting LocalDateTime as it doesn't contain any TZ information.
>
>
> That's not very easy to do since either the JDBC Driver or the database
> engine might to the
e-core/blob/wip/6.0/logger_id_ranges.adoc
Awesome!
Thanks,
Sanne
>
> On Fri, Sep 28, 2018 at 10:35 AM Sanne Grinovero wrote:
>>
>> Hi Steve,
>>
>> I love the cathegories idea; I think we discussed it before. My only
>> concern is that it's a lot of work to imp
Hi Steve,
I love the cathegories idea; I think we discussed it before. My only
concern is that it's a lot of work to implement, but if you feel it's
doable that's great.
In terms of "changes needed" I'm not worried either. Like you said, 6
would have had different names for most cases; at least
Thanks Rory!
we have no specific problems to report, yet users will need to be
aware of some changes but I guess that's of no surprise to you all.
One is that people won't be able to blindly rely on our dependencies
being defined by Maven descriptors, as the dependencies need to be
different on
Thanks Rory!
Updating our systems.
Regards,
Sanne
On Fri, 24 Aug 2018 at 10:25, Rory O'Donnell wrote:
>
> Hi Sanne,
>
> *JDK 11 build 28 is our first JDK 11 Release Candidate [1]
> *
>
> * JDK 11 Early Access build 28 is available at : - jdk.java.net/11/
>
> *FOSS fixes in recent builds.*
>
On Thu, 16 Aug 2018 at 15:18, Guillaume Smet wrote:
>
> On Thu, Aug 16, 2018 at 4:05 PM Sanne Grinovero wrote:
>>
>> It's never realistic to say "it's THE last ..." so I guess I agree we
>> can show a bit of flexibility - but people should not get used to it,
It's never realistic to say "it's THE last ..." so I guess I agree we
can show a bit of flexibility - but people should not get used to it,
we can not re-establish a plan of regular releases from 5.2.
We have to severely limit the time we can dedicate to it. Also please
make sure people are
t; against removing them though if you wish.
>
> If we go this route of statically implementing JDBC contracts, then another
> one to consider is ResultSetWrapperProxy..
>
> On Wed, Aug 15, 2018 at 2:26 PM Sanne Grinovero wrote:
>>
>> I'm trying
I'm trying to understand if we could remove some of the usages of
`java.lang.reflect.Proxy`.
Clearly it's a long journey and maybe we will never be able to remove
them all, but I would at least want to try avoiding most of their neet
at runtime - limiting their usage at bootstrap/configuration or
Hi all,
we have these new databases running on AWS now:
- SQL Server Express Edition 14.00.3015.40.v1
- Oracle Standard Edition Two 12.1.0.2.v12
CI jobs are setup for Hibernate ORM to watch the master branch;
connection settings are committed in ORM's upstream.
See the usual matrix
ferrable via normal Gradle means.
> Seems by far easier solution...
I hope you like this? It was easy enough, once I learned about it:
-
https://github.com/hibernate/hibernate-orm/blob/cd8b754494617e722097d3612f9bdde7a17710aa/build.gradle#L43-L49
>
>
> On Thu, Aug 9, 2018 at 9:42 AM Sanne
I'm setting up some new Oracle integration tests on ci.hibernate.org,
and we're having again a similar issue to what we had with SAP HANA:
- some JDBC drivers can not be distributed freely
- we do not want to allow the Hibernate ORM build to load
dependencies from a local Maven repository
So
+1
I think we can live with minor inconveniences, especially as I hope
we'll be moving more projects to take advantage of the pipelines.
On Thu, 2 Aug 2018 at 17:56, Yoann Rodiere wrote:
>
> Hi,
>
> We're about to make use of Jenkins pipelines in Hibernate Search, and for
> that purpose, the
This class seems to have a single purpose, which is to extract a
constant from the Oracle JDBC driver:
-
https://github.com/hibernate/hibernate-orm/blob/bd256e4783219f4a765219cf625bb658fcb5fde1/hibernate-core/src/main/java/org/hibernate/dialect/OracleTypesHelper.java#L20
Would it be possible to
Please be mindful of SEO as well. All existing valid URLs should
redirect to a valid HTTPS alternative before we switch.
On Mon, 30 Jul 2018 at 16:41, Guillaume Smet wrote:
>
> Please don't do it: there's a good reason I haven't done it: the news are
> not loaded because in.relation.to is not
+1 to test Zulip, thanks for setting it up Yoann.
Personally having used it quite a bit with other projects: it has
potential but it's not particularly polished yet; in particular the
mobile client has severe issues, and people are quite often failing to
use the "topics" correctly.
In the news
On Tue, 17 Jul 2018 at 13:45, Guillaume Smet wrote:
>
> Hi,
>
> On Tue, Jul 17, 2018 at 11:33 AM Sanne Grinovero wrote:
>>
>> In the specific example of HHH-3138, I guess people didn't comment as
>> there is no clear problem to be solved. It might help to expla
Hi Alvaro,
welcome :-)
The ticket descriptions can be debated; we can all be wrong, or you
might have a better idea.
Regarding feedback times: I'm sorry we're a bit slow. There are many
things which are urgent - or we're more interested in - and since it's
summer so many are on holidays. It
On Mon, 9 Jul 2018 at 16:09, Guillaume Smet wrote:
>
> On Mon, Jul 9, 2018 at 4:56 PM Sanne Grinovero wrote:
>>
>> send a PR, the bots will trigger test runs at least for Java 8.
>
>
> Do we run all the tests with Javassist now that Bytebuddy is the default?
No, but
Hi Scott,
send a PR, the bots will trigger test runs at least for Java 8.
For proper JDK11 testing that will have to wait as other things aren't
working yet, but if the Javassist update works flawlessly on Java 8
there is no reason to not update this point already.
Thanks,
Sanne
On Mon, 9 Jul
'd be willing to push to the next Alpha
>>
>> On Mon, Jul 2, 2018 at 10:42 AM Sanne Grinovero wrote:
>>>
>>> On Hibernate ORM we're currently having "master" branch essentially
>>> being a maintenance branch, aka master today is what's planned to be
>
On Hibernate ORM we're currently having "master" branch essentially
being a maintenance branch, aka master today is what's planned to be
version 5.3.2.Final in some days, 5.3.3 later, etc..
This is quite unusual, and it begs some extra attention: normally we'd
start a new minor in master, so that
On Tue, 19 Jun 2018 at 16:32, Emmanuel Bernard wrote:
>
> On Tue 18-06-19 15:13, Sanne Grinovero wrote:
> >On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard
> >wrote:
> >>
> >>
> >>
> >> > On 18 Jun 2018, at 17:49, Sanne Grinovero wro
On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard wrote:
>
>
>
> > On 18 Jun 2018, at 17:49, Sanne Grinovero wrote:
> >
> > I was experimenting with "let's encrypt" but then you told me that I
> > wasn't allowed to use that service.
>
> I don’t r
On Sat, 16 Jun 2018 at 18:51, Emmanuel Bernard wrote:
>
> Let’s wait quickly for Sanne’s feedback on why he was having certificate
> issues. My experience with let’s encrypt has been stellar so far (httpd).
I was experimenting with "let's encrypt" but then you told me that I
wasn't allowed to
Just an update: Steve and Andrea helped me and we got it done.
We can finally run the full build on JDK10; for JDK11 we still need to
sort out some details, e.g. yet another Gradle update.
On Fri, 8 Jun 2018 at 10:12, Sanne Grinovero wrote:
>
> I previously upgraded Hibernate ORM to Grad
I previously upgraded Hibernate ORM to Gradle 4.7, that was trivial.
I'd like us to upgrade to 4.8 (now also released) so to keep going
testing with JDK11 - but I got some puzzling errors with the Gradle
build to remind me that this is still beyond my Gradle-fu :)
If someone else could take [1]
00, Rory O'Donnell wrote:
>>
>> Thanks Sanne, we are looking into it.
>>
>> Rgds,Rory
>>
>>
>> On 31/05/2018 15:59, Sanne Grinovero wrote:
>>>
>>> Hi Rory,
>>>
>>> I was trying to download the OpenJDK / Linux distribution from
>
On 6 June 2018 at 12:04, Guillaume Smet wrote:
> On Wed, Jun 6, 2018 at 12:57 PM Sanne Grinovero wrote:
>>
>> Just curious, did that really work consistently?
>
>
> Well, it works consistently as in if your issue is in the "Pull request
> sent" status,
Just curious, did that really work consistently?
As far as I know, the JIRA integration was never really able to match
GitHub PR changes to JIRA issues reliably.
On 6 June 2018 at 11:37, Guillaume Smet wrote:
> Hi,
>
> A few months back, when an issue was in the "Pull request sent" status, it
>
On 5 June 2018 at 14:43, Scott Marlow wrote:
> The PersistenceUnitInfo#addTransformer javadoc [1] mentions:
>
> "
> Add a transformer supplied by the provider that will be called for every
> new class definition or class redefinition that gets loaded by the loader
> returned by the
On 4 June 2018 at 12:23, Tom Jenkinson wrote:
>
>
> On 28 May 2018 at 12:23, Sanne Grinovero wrote:
>>
>> On 28 May 2018 at 00:05, Steve Ebersole wrote:
>> > JBossStandalone is meant for use of JBoss Transactions outside of
>> > WildFly.
>> > Why
101 - 200 of 2025 matches
Mail list logo
