Well I guess I got my feedback :) Sorry I did not know it was on
purpose, I don't remember reading it on the mailing list.
So with enforced HTTPS off, we need to go a chase all the links in the
form of https://hibernate.org/foo and make them
https://hibernate.org/foo/ due to a limitation in GitHub
Hi all,
I'm seeing plenty of code has been refactored in recent years to use a
" public static final X INSTANCE" field rather than a normal
constructor.
Often this is a good thing since memory allocation rate is *typically*
our limiting factor to improve performance, yet let's be mindful that
thi
FWIW, I reverted it.
On Mon, Jul 30, 2018 at 6:33 PM Yoann Rodiere wrote:
> Also several users just reported that some wrong URL (
> http://hibernate.org/hibernate-configuration-3.0.dtd) used to work, and
> now doesn't. It started very recently.
>
> Did you change some HTTP redirection rules? Or
Also several users just reported that some wrong URL (
http://hibernate.org/hibernate-configuration-3.0.dtd) used to work, and now
doesn't. It started very recently.
Did you change some HTTP redirection rules? Or maybe we had a redirection
from http://hibernate.org/hibernate-configuration-3.0.dtd
If we must compare Zulip to emails, cross-posting to multiple mailing lists
would be equivalent to posting to different "streams", which are the
equivalent of "rooms" in HipChat or "channels" in IRC.
Short answer is: you can't do that, you have to duplicate the conversation.
But so would you in Hip
On Mon, 30 Jul 2018 at 16:39, Steve Ebersole wrote:
>
> I am not asking about a "supart". Think about topics that we cross post to
> hibernate-dev and willdfly-dev or hibernate-dev and infinispan-dev... so
> the discussion *simultaneously* spans multiple topics/audiences.
In zulip what you write
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 HTTP
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 HTTPS.
We need to enable HTTPS for in.relation.to before doing it.
Thanks.
On Mon, Jul 30, 2018 at 4:43 PM Emmanuel Bernard
wrote:
> I've enforced HTTPS on hibernate.org.
> I am
I am not asking about a "supart". Think about topics that we cross post to
hibernate-dev and willdfly-dev or hibernate-dev and infinispan-dev... so
the discussion *simultaneously* spans multiple topics/audiences.
On Mon, Jul 30, 2018 at 9:27 AM Emmanuel Bernard
wrote:
> Same as in an email thre
Same as in an email thread, you change the topic for a subpart of your
conversation. You can opt to fork the topic name at a
given point in time retroactively (which you don't get for emails).
On Mon 18-07-30 9:10, Steve Ebersole wrote:
>In practice, what happens when a discussion spans multiple
I've enforced HTTPS on hibernate.org.
I am aware that Google Chrome shows warning as we load some non HTTPS
resources as part of the pages (two images, one link and the
in.relation.to feed).
But if you see other things not working, let us know.
Here is the issue tracker
https://hibernate.atlassian
In practice, what happens when a discussion spans multiple topics?
On Fri, Jul 27, 2018 at 9:43 AM Emmanuel Bernard
wrote:
> On Fri 18-07-27 14:38, Guillaume Smet wrote:
> >On Fri, Jul 27, 2018 at 2:31 PM Emmanuel Bernard
> >wrote:
> >
> >> I like Zulip a lot. I've been using it extensively an
It is equivalent to `javax.persistence.Cacheable(false)`, although it was
never well defined what it means in relation to
`javax.persistence.SharedCacheMode`
On Mon, Jul 30, 2018 at 5:40 AM Guillaume Smet
wrote:
> Hi,
>
> Does setting @Cache(usage = CacheConcurrencyStrategy.NONE) on an entity
>
Hi,
Does setting @Cache(usage = CacheConcurrencyStrategy.NONE) on an entity
mean that we entirely disable the 2nd level cache for this entity?
The documentation does not reference this value and the Javadoc does not
state clearly that the cache is disabled with this concurrency strategy.
Asking
14 matches
Mail list logo
