Apart from migration concerns, is anything in Lucene 6 allowing us to
provide new exciting functionality to users?
2016-04-04 17:23 GMT+02:00 Emmanuel Bernard :
> +1
>
> On Mon 2016-04-04 14:02, Sanne Grinovero wrote:
> > The Apache Lucene team is voting on candidate releases for Lucene 6.0.0.
>
It should be possible to make it work rendered *and* when previewed on
GitHub by defining a suffix for links if you are in the "GitHub
environment":
ifdef::env-github[:outfilesuffix: .adoc]
See https://github.com/asciidoctor/asciidoctor/issues/417 and
https://github.com/opendevise/asciidoc-sa
Hi Gail,
I removed the 5.1 references on the new User Guide.
You can check it out and see how you like it:
> cd documentation
> gradle rUG
Let me know what you think.
Vlad
On Mon, Apr 4, 2016 at 11:02 PM, Gail Badner wrote:
> Thanks much!
>
> On Mon, Apr 4, 2016 at 11:48 AM, Vlad Mihalcea
>
Thanks much!
On Mon, Apr 4, 2016 at 11:48 AM, Vlad Mihalcea
wrote:
> Sure,
>
> I'm going to take care of it tomorrow.
>
> Vlad
>
> On Mon, Apr 4, 2016 at 9:33 PM, Gail Badner wrote:
>
>> Is there is any 5.1-specific content? If so, it needs to be stripped out
>> for 5.0.
>>
>> On Mon, Apr 4, 20
Sure,
I'm going to take care of it tomorrow.
Vlad
On Mon, Apr 4, 2016 at 9:33 PM, Gail Badner wrote:
> Is there is any 5.1-specific content? If so, it needs to be stripped out
> for 5.0.
>
> On Mon, Apr 4, 2016 at 6:35 AM, Vlad Mihalcea
> wrote:
>
>> Hi Gail,
>>
>> I pushed the 5.1 documentat
Is there is any 5.1-specific content? If so, it needs to be stripped out
for 5.0.
On Mon, Apr 4, 2016 at 6:35 AM, Vlad Mihalcea
wrote:
> Hi Gail,
>
> I pushed the 5.1 documentation into the 5,0 branch.
> The only thing that's needed now is to modify the release procedure which
> I'll send it as
Yes I think that's reasonable.
My gut feeling is that there are only a handful HibernateException
subclass really useful when coding an application, breaking the rest is
probably fine.
On Mon 2016-04-04 15:55, Steve Ebersole wrote:
> So to me the biggest design question is in regard to exceptions.
On 04/04/2016 11:36 AM, Sanne Grinovero wrote:
> On 4 April 2016 at 15:48, Steve Ebersole wrote:
>> So there we go :)
>>
>> On Mon, Apr 4, 2016 at 9:37 AM Scott Marlow wrote:
>>>
>>> Hmm, just searched through irc history and came up with fixed by
>>> https://hibernate.atlassian.net/browse/HHH-
So to me the biggest design question is in regard to exceptions. Where
possible I plan on integrating the 2 hierarchies (which probably means the
Hibernate exceptions becoming interfaces). In cases where such an
integration is not possible we will have to err on the side of preferring
the JPA exc
On 4 April 2016 at 15:48, Steve Ebersole wrote:
> So there we go :)
>
> On Mon, Apr 4, 2016 at 9:37 AM Scott Marlow wrote:
>>
>> Hmm, just searched through irc history and came up with fixed by
>> https://hibernate.atlassian.net/browse/HHH-7552. Nice to see this
>> already fixed! ;)
Great, so
I don't think I would equate reactive and CQRS, but reactive (say in the
Rx sense) definitely goes for a more action centric persistence than an
ORM centric persistence.
I did explore only a little bit but I could not fully re conciliate a Rx
centric API with the idea of a (extra)-transaction bound
+1
On Mon 2016-04-04 14:02, Sanne Grinovero wrote:
> The Apache Lucene team is voting on candidate releases for Lucene 6.0.0.
>
> As usual we'll refrain from making API changes in a minor release, but
> we should start to sometimes try building against Lucene 6 to make
> sure to use APIs which wi
I liked the idea of the README as a proper webpage. But I can live
without it and I don't have strong grounded arguments for it.
On Mon 2016-04-04 10:52, Sanne Grinovero wrote:
> It sounds good to me in principle, but I vaguely remember we
> intentionally added that README to the website for some
So there we go :)
On Mon, Apr 4, 2016 at 9:37 AM Scott Marlow wrote:
> Hmm, just searched through irc history and came up with fixed by
> https://hibernate.atlassian.net/browse/HHH-7552. Nice to see this
> already fixed! ;)
>
> On 04/04/2016 10:32 AM, Steve Ebersole wrote:
> > Ok, so we aren't
Hmm, just searched through irc history and came up with fixed by
https://hibernate.atlassian.net/browse/HHH-7552. Nice to see this
already fixed! ;)
On 04/04/2016 10:32 AM, Steve Ebersole wrote:
> Ok, so we aren't accepting a Class reference or instance for L2C
> RegionFactory? Is there a Jir
Ok, so we aren't accepting a Class reference or instance for L2C
RegionFactory? Is there a Jira for that?
On Mon, Apr 4, 2016 at 9:20 AM Scott Marlow wrote:
> On 04/04/2016 08:55 AM, Sanne Grinovero wrote:
> > On 4 April 2016 at 12:59, Gunnar Morling wrote:
> >> One minor wish I'd have around
On 04/04/2016 08:55 AM, Sanne Grinovero wrote:
> On 4 April 2016 at 12:59, Gunnar Morling wrote:
>> One minor wish I'd have around bootstrapping:
>>
>> Can we make the initiators of services residing in the session factory
>> service registry discoverable by means of a ServiceContributor as it's
>
Hi Gail,
I pushed the 5.1 documentation into the 5,0 branch.
The only thing that's needed now is to modify the release procedure which
I'll send it as a PR.
We also have to modify the hibernate.org site so that 5.0 references the
same documentation links as 5.1.
Vlad
On Thu, Mar 24, 2016 at 7:3
Now there is: https://hibernate.atlassian.net/browse/HHH-10669 :)
Thanks!
2016-04-04 15:08 GMT+02:00 Steve Ebersole :
> I think this is reasonable. Is there a Jira for it?
>
>
> On Mon, Apr 4, 2016, 6:59 AM Gunnar Morling wrote:
>
>> One minor wish I'd have around bootstrapping:
>>
>> Can we m
On 4 April 2016 at 14:07, Steve Ebersole wrote:
> JtaPlatform can already be injected by instance. In general, depending on
> the service initiator, most services can be specified as either name, Class
> or instance. Many configuration values as well.
>
> That's something I have been doing for ye
I think this is reasonable. Is there a Jira for it?
On Mon, Apr 4, 2016, 6:59 AM Gunnar Morling wrote:
> One minor wish I'd have around bootstrapping:
>
> Can we make the initiators of services residing in the session factory
> service registry discoverable by means of a ServiceContributor as i
JtaPlatform can already be injected by instance. In general, depending on
the service initiator, most services can be specified as either name, Class
or instance. Many configuration values as well.
That's something I have been doing for years.
On Mon, Apr 4, 2016, 7:57 AM Sanne Grinovero wrote:
The Apache Lucene team is voting on candidate releases for Lucene 6.0.0.
As usual we'll refrain from making API changes in a minor release, but
we should start to sometimes try building against Lucene 6 to make
sure to use APIs which will live longer, if there's choice.
The most notable change is
On 4 April 2016 at 12:59, Gunnar Morling wrote:
> One minor wish I'd have around bootstrapping:
>
> Can we make the initiators of services residing in the session factory
> service registry discoverable by means of a ServiceContributor as it's
> happening for services living in the standard regist
One minor wish I'd have around bootstrapping:
Can we make the initiators of services residing in the session factory
service registry discoverable by means of a ServiceContributor as it's
happening for services living in the standard registry?
Currently, it's a hard coded list, requiring Hibernat
It sounds good to me in principle, but I vaguely remember we
intentionally added that README to the website for some reason.
I don't remember what the reason was exactly though, so my doubt is
that we're actually linking to that URL from somewhere.
Let's not rush it and wait for several more opini
Hi,
While setting up my environment for hibernate.org and in.relation.to, I
noticed that there are broken links in the README... when we read it on
GitHub (the .adoc extension is missing). It works OK when we read it from
the website using http://hibernate.org/README/.
I expect most people to use
27 matches
Mail list logo
