Hi Mincong,
Gunnar suggested that I find a first task for you to familiarize with
the project, and to have you practice the process of creating patches
and proposing them for integration over GitHub.
I think this issue could be suited:
- https://hibernate.atlassian.net/browse/HSEARCH-2207
I
Github now offers an option to not create the "merge commit" when you
want to merge a PR from the web ui.
It comes at a significant cost though: it will merge the PR but squash
all commits in one.
While initially thinking that doesn't help us at all, at second
thought: we really want any
Sounds reasonable. Do you think it will be unstable, i.e. should we
temporarily disable complaint emails from Jenkins, or even the full
build tasks?
Also, this implies that any future backport becomes similarly harder,
so you could also simply ask others to hold pushing on master, then
have
Hi,
I was hoping that even w/o a specific OGM sprint we would soon (next
week?) be able to re-spin the CR1 with minor effort as the
5.0.0.Final.
Among tasks scheduled for 5.0.0.Final:
-
On 5 April 2016 at 14:11, Vlad Mihalcea wrote:
> Hi,
>
> While reviewing the PR for this issue:
>
> https://hibernate.atlassian.net/browse/HHH-10649
>
> I realized that the ReadWrite cache concurrency strategy has a flaw that
> permits "read uncommitted" anomalies.
> The
eed.
Thanks,
Sanne
>
> 2016-04-04 17:23 GMT+02:00 Emmanuel Bernard <emman...@hibernate.org>:
>>
>> +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.
>> >
>
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
t; That's something I have been doing for years.
Cool, then I'm mistaken about which component it was, just that Scott
mentioned it would be nice to inject something which was currently not
the case. Maybe my memory is years outdated? Scott?
Thanks,
Sanne
>
>
> On Mon, Apr 4, 201
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
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
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
I just merged Davide's work. Make sure you cleanup the old
directories, as git will leave the stale files from previous builds.
Thanks Davide!
Sanne
On 24 March 2016 at 10:30, Davide D'Alto wrote:
> Yes, I'll have a look at this
>
> Davide
>
> On Thu, Mar 24, 2016 at
ntation.
So, should we rather ask Scott to remove that OGM support code from WildFly?
I'd rather have WildFly add all the modules, at least people can
forget about this.
Thanks,
Sanne
>
> On Thu, Mar 31, 2016 at 7:39 AM, Gunnar Morling <gun...@hibernate.org>
> wrote:
>>
On 30 Mar 2016 21:11, "Scott Marlow" <smar...@redhat.com> wrote:
>
>
>
> On 03/30/2016 12:15 PM, Sanne Grinovero wrote:
>>
>> I'm reviewing how we expect people to use the Hibernate OGM modules on
WildFly.
>>
>> Scott mentioned
On 30 March 2016 at 18:35, Davide D'Alto wrote:
> I don't think I like the idea of adding unnecessary dependencies on the user
> classpath.
I don't like it either, but specifically why not?
It would be less "magic" which is usually a good thing in these complex systems.
>
I'm reviewing how we expect people to use the Hibernate OGM modules on WildFly.
Scott mentioned that the JPA subsystem of WildFly automatically adds
the "org.hibernate.ogm" module when the
org.hibernate.ogm.jpa.HibernateOgmPersistence persistence provider is
set.
See also :
-
+1
My personal opinion is that we should switch to Java8 for our next-gen platform.
On top of the cool point on default methods you mention, it should
also make it easier to start polishing our APIs to have end users take
advantage of Java8 features.
Not least, next version of Apache Lucene will
lassian.net/browse/HHH-10657
Sanne
>
> Vlad
>
> On Mon, Mar 21, 2016 at 4:43 PM, Sanne Grinovero <sa...@hibernate.org>
> wrote:
>>
>> Hello all,
>> I've often used, and see others use, the value "none" for the property
>> hibernate.hbm2dd
When using Hibernate OGM on WildFly it's currently necessary to set
this property:
hibernate.transaction.jta.platform = JBossAS
1 -- Would you all be ok for me to add a "WildFly" alias which
resolves to the same implementation?
This would be a patch for Hibernate ORM so it affects everyone.
nar
>
> PS: We seem to switch between "ScenicDrive" and "ScenicView" ;) In my PoC I
> went for the latter.
>
>
>
>
>
> 2016-03-23 19:28 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> On 23 March 2016 at 17:18, Emmanuel Bernar
olations which CS failed to report. Must have been these bug fixes then.
>>
>> The only thing coming to my mind is Davide's work which may change things
>> in the existing Neo4j code. Maybe you two quickly sync? Apart from that
>> I'd
>> say let's do it.
>>
>> 2016-03-2
f you're going to have better decision elements after your
POC, or if having the POC separate is setting the first irreversible
note.
Some people suggest that a POC should always be thrown away and rewritten...
Sanne
>
>
>
>
>
> 2016-03-23 19:28 GMT+01:00 Sanne Grinovero <
On 23 March 2016 at 17:18, Emmanuel Bernard wrote:
> Is ScenicDrive captured?
Interesting. You suggest that ScenicDrive is a feature of OGM ?
>
> On Tue 2016-03-22 11:29, Davide D'Alto wrote:
>> Next JIRA will be OGM-1000, any interesting idea we should use for this
>>
Hi Emmanuel,
as you'll meet the right people this week, could you find a minute to
chat about what the plan is around feature packs and how that should
evolve, especially how it relates to WildFly Swarm?
https://hibernate.atlassian.net/browse/HSEARCH-2191
Thanks,
Sanne
Hello all,
I've often used, and see others use, the value "none" for the property
hibernate.hbm2ddl.auto.
In recent versions of Hibernate ORM I now get the following warning:
[WARN] SessionFactoryBuilderImpl: Unrecognized hbm2ddl_auto value :
none. Supported values include create, create-drop,
didn't we have a validation in place for tags?
>
>
>
>
> On Mon, Mar 21, 2016 at 1:51 PM, Sanne Grinovero <sa...@hibernate.org>
> wrote:
>
>> Sorry that restriction wasn't clear to me.
>>
>> Could we wait some time before deleting it?
>> I'm afraid I
Sorry that restriction wasn't clear to me.
Could we wait some time before deleting it?
I'm afraid I shared that link on social media, e.g. the Elasticsearch forums.
BTW It's not clear to me why you fear an explosion; having a tag cloud
is not uncommon on blogs, and is based on the idea of having
On 17 March 2016 at 17:40, Steve Ebersole wrote:
> To be honest, I think its best if we somehow notify you for issues fixed
> that we think should be considered for inclusion on 5.0 branch and you can
> decide. A label or a filter. Something like that
+1 Shouldn't any bug
Hello team,
I've started making several improvements for the Hibernate OGM Quick
Start on the hibernate.org website;
I got side-tracked to test it all, but also the new version will
assume that we already released version 5.0.0.Final so I'll hold the
changes for until the release - or shortly
Hello all,
we released the third milestone of our work towards a great
integration with Elasticsearch:
Hibernate Search 5.6.0.Alpha3.
See also:
- http://in.relation.to/2016/03/17/ThirdAlphaElasticsearch/
Regards,
Sanne
___
hibernate-dev mailing list
s up to those who do the job to decide..
But dropping 5.0 seems way premature to me to the point that I'd rather
slow down other R
>
> 2016-03-17 22:17 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
> > On 17 March 2016 at 17:40, Steve Ebersole <st...@hibernate.org> wrote:
>
On 15 March 2016 at 17:21, Davide D'Alto wrote:
> At the moment the elasticsearch integration artifactid is:
>
> hibernate-search-backend-elasticsearch
>
> Elasticsearch is actually more than just a backend (we use this term for
> the jGroups and JMS integration). I think we
I remember JBoss had "HAR" deployments to package Hibernate models and
PU definitions.. as far as I know this was a JBoss only thing, it
wouldn't surprise me if other app servers experimented with similar
non-standardized archives.
https://docs.jboss.org/jbossas/jboss4guide/r3/html/ch13.html
On
ference documentation and try thinking ahead of what problems that
will introduce.
I didn't find any point which wouldn't be easy to dismiss but a second
pair of brains would be nice on this ;)
Thanks,
Sanne
>
>
> --Gunnar
>
> 2016-03-08 12:55 GMT+01:00 Sanne Grinovero <sa...@hib
Today our experiments are assuming we're connecting to a single
Elasticsearch cluster: one hostname to configure, etc..
I think this is an acceptable limitation for version 5.6 (our first
stable milestone to support this integration) but I'm wondering if we
should document it as a temporary
On 5 March 2016 at 22:04, Marc Schipperheyn wrote:
> I saw the elastic search blog post and while is not yet sonething on our
> radar, it s certainly interesting!
>
> I already saw that if you bypass HSearch to go native, the syntax changes.
> What about Lucene
bernate.org>:
>> Ahaha, ok. I took previous contribution as a given for active
>> participants on hibernate-dev and people considering to mentor ;)
>> Sorry I misread.
>>
>> 2016-03-03 12:38 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>>&g
we think that clears the path.
Allowing them on a field obviously makes not much harm; I wouldn't
pursue any changes at all if it weren't for the idea of needing an
entirely new annotation to shield user code from Lucene classes (the
next point).
>
> On Thu 2016-03-03 15:08, Sanne
On 3 March 2016 at 16:53, Emmanuel Bernard wrote:
> Regardless of the queue approach you want in the future, it should not
> be coupled with Elasticsearch's effort.
> It's an orthogonal concern on how to decouple work generation from work
> consumption.
> That way we can
On 3 March 2016 at 15:11, Emmanuel Bernard <emman...@hibernate.org> wrote:
> On Thu 2016-03-03 14:19, Sanne Grinovero wrote:
>> Back to my Elasticsearch problem: I think the short term solution
>> would be that we actually have to check for the index state after
>>
I just realized that the definiton for @AnalyzerDef allows many target ypes:
@Target({ ElementType.PACKAGE, ElementType.TYPE, ElementType.FIELD,
ElementType.METHOD })
I think FIELD and METHOD might not have been intended to be there.
Should we correct this in 6 to
@Target({
My question here was triggered by a specific case in Hibernate Search
but it applies well to ORM's datasources, caches, and very much to OGM
as well.
When creating an index on Elasticsearch, the index is not
"instantaneously" ready.
The REST request creates the definition, but the response will
area doesn't harm, but it's no
> requirement. Much more important is the general attitude (willingness
> to learn etc.) as well as general programming knowledge.
>
> Student's applications start on March 14th, so whatever we feel like
> going for, should be in that proposal lis
..@gmail.com>
> wrote:
>>
>> Hi Sanne,
>>
>> On Thu, Jan 28, 2016 at 3:23 PM, Sanne Grinovero <sa...@hibernate.org>
>> wrote:
>>>
>>> I am a bit skeptical as we have CI working already on ci.hibernate.org
>>> and having li
Java 8 so limiting hibernate-infinispan to > 8 really
>> makes
>> > no sense,
>> >
>> > On Tue, Mar 1, 2016 at 3:03 PM Sanne Grinovero <sa...@hibernate.org>
>> wrote:
>> >
>> >> In general, probably yes. The Infinispan modul
Awesome news! Thanks for letting us know.
On 1 March 2016 at 21:16, Steve Ebersole wrote:
> Today Andrea and I spent the day investigating interpreting of HQL/JPQL
> into SQM in just a single phase as opposed to the previous 2-phase approach
> (all FromClauses as first
In general, probably yes. The Infinispan module is a bit special
though, as Infinispan itself requires Java8 since Infinispan 8 so
noone will be able to use those modules on previous Java versions.. so
there's no point in avoiding pre-Java 8 code in there.
On 1 March 2016 at 20:55, Gail Badner
Hi all,
earlier today in our IRC meeting [1] we discussed ideas for Google
Summer of Code;
mostly related Hibernate Search but not only:
Quoting the previous summary by Gunnar:
1 - Java Batch API job for HSEARCH mass indexing
2 - Solr backend
3 - HSEARCH support for JHipster
4 - HSEARCH
the tests only take 25
>> minutes:
>>
>> http://ci.hibernate.org/job/hibernate-orm-master-h2/1392/testReport/
>>
>> Could that check style plugin cause this issue?
>>
>> Vlad
>>
>> On Tue, Mar 1, 2016 at 3:06 PM, Sanne Grinovero <sa...@hibernate
> 2016-02-29 7:48 GMT+01:00 Gunnar Morling <gun...@hibernate.org>:
>> Awesome! The docs look great, thanks a lot!
>>
>> +100 for pushing this out, I think it's ready for that.
>>
>> Cheers guys,
>>
>> --Gunnar
>>
>>
>>
>> 20
Hi all,
Martin has been contributing to Hibernate Search since a year, and
developed some very interesting extensions this summer in the scope of
Google Summer of Code, and is still
evolving those and generally helping and monitoring the project.
He recently volunteered to try helping us with
On 25 February 2016 at 17:16, Guillaume Smet wrote:
> Hi,
>
> Running the DSLTest is quite interesting as it runs a lot of different
> queries with different configurations.
>
> Here are some thoughts while working on it.
>
> 1/ Analyzers
> =
>
> Gunnar, I was
On 25 February 2016 at 15:37, Gunnar Morling <gun...@hibernate.org> wrote:
> 2016-02-25 16:28 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>> On 25 February 2016 at 15:14, Gunnar Morling <gun...@hibernate.org> wrote:
>>> It's Monday morning.
>>&g
ome..
Sanne
>
> WDYT?
>
> --Gunnar
>
>
>
>
> 2016-02-25 16:06 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>> On 25 February 2016 at 15:03, Gunnar Morling <gun...@hibernate.org> wrote:
>>> Hi Guillaume,
>>>
>>> Yes, that s
On 25 February 2016 at 15:03, Gunnar Morling wrote:
> Hi Guillaume,
>
> Yes, that seems reasonable. Thanks for fixing it!
>
> @Sanne, can we aim for another Alpha release tomorrow? Then I can show
> released bits in my talk :)
+1. When exactly is your presentation? I'd like
We're doing fast iterations on the experimental Elasticsearch support
for Hibernate Search,
and by doing so there have been introduced temporary changes so we can
make progress while sharing code with each other.
CI is used to highly polished code, so it's failing the builds for
petty warning
It sounds interesting, but bear with me I'm not familiar with it so
I'll throw out some doubts.
Will it work without a JEE container?
I guess some implementations might be embeddable, but still how simple
would that be for the user?
Note that we already allow rebuilding the index via JMX
On 23 February 2016 at 19:26, Guillaume Smet <guillaume.s...@gmail.com> wrote:
> On Tue, Feb 23, 2016 at 7:21 PM, Sanne Grinovero <sa...@hibernate.org>
> wrote:
>>
>> I don't have a strong opinion on the usefulness on faceting on null;
>> would someone
I don't have a strong opinion on the usefulness on faceting on null;
would someone have a sensible example of faceting on a "null value" ?
We can fix it but I have the impression it's just about fixing a
developer's itch because of it being inconsistent with other
components; if it helps with
+1
Avoiding a runtime dependency seems far better than shading. Maybe the same
could be done with Javassist?
On Wed, 17 Feb 2016 12:15 Gunnar Morling wrote:
> Hi,
>
> I'd like to propose an alternative approach for proxy generation which
> would avoid version issues with
Congratulations!!
On 10 February 2016 at 18:16, Steve Ebersole wrote:
> The release build is done. Push away!
>
>
> On Wed, Feb 10, 2016 at 11:14 AM Steve Ebersole wrote:
>
>>
>>
> ___
> hibernate-dev mailing
On 8 February 2016 at 17:44, Steve Ebersole wrote:
> I am working mainly on HHH-16 which requests adding support for
> entity-joins (aka "ad hoc" joins).
>
> So long-story-short, there is a simple solution with some limitations and
> then a more correct solution that
Good catch!
Make sure to open a JIRA issue as first step, to not forget about this
even in case you get distracted.
On 3 February 2016 at 11:10, Guillaume Smet wrote:
> On Wed, Feb 3, 2016 at 11:45 AM, Hardy Ferentschik
> wrote:
>
>> Sounds like an
Hi Scott,
I'm missing something here: I think there is a 3rd option which is to
not require the user's classpath to "see" the Javassist at all, even
though Hibernate uses it.
But I've said this before in other context, and yet we're back at
discussing only options 1 and 2, so I'm guessing that we
don't have them.
For the record, people should be able to use JPA in WildFly without
being able to see any org.hibernate class too.
Sanne
>
> On Wed 2016-02-03 14:02, Sanne Grinovero wrote:
>> Hi Scott,
>> I'm missing something here: I think there is a 3rd option which is to
>> n
+1 to approve any reasonable request to join us.
I think the functionality is there only to be prevent spammers and
kick out misbehaving people; we have no intent of keeping any
goodwilling developer out.
On 2 February 2016 at 12:49, Davide D'Alto wrote:
> I was wrong about
I would think that such a tool would work at compile time rather than
reflectively at runtime, but one can't be sure of course so it depends
on what you have in mind.
I'd also say make @Incubating with CLASS retention, it's more than
what people had before.. you can always evolve it later if
Thanks! that looks like a very good idea.
On 28 January 2016 at 05:48, Vlad Mihalcea wrote:
> I created this JIRA issue for this:
>
> https://hibernate.atlassian.net/browse/HHH-10483
>
> Vlad
>
> On Wed, Jan 27, 2016 at 7:02 PM, Vlad Mihalcea
Hi Guillaume,
I am a bit skeptical as we have CI working already on ci.hibernate.org
and having limited people we can't really afford to fix things which
already work.
That said, this does look good, and it's certainly positive that we
can get some free computation resources from travis.org as our
Hello all,
I'm thrilled to announce that there is now Eclipse tooling available
to help developers using Hibernate Search.
This was created by Dmitry Bocharov, started this summer as a GSOC
summer of code and still volunteering on it.
Better described in his own words on our blog:
-
List multiLoad(Serializable[] ids, SessionImplementor session,
> MultiLoadOptions loadOptions);
>
> MultiLoadOptions encapsulates the information configured
> on MultiIdentifierLoadAccess.
>
> At this point, I am calling this work done.
>
> On Mon, Jan 25, 2016 at 12:30 PM S
I checked :
- Hibernate OGM
- Hibernate Search
- Hibernate Validator
- WildFly
And none are using the listeners you listed. In the case of WildFly, I
don't know of course about all the frameworks which are included in
there.
Sanne
On 22 January 2016 at 23:58, Steve Ebersole
split off into a new contract, is maybe
> MultiIdentifierLoadAccess#load preferable over
> MultiIdentifierLoadAccess#multiLoad?
>
> On Wed, Jan 20, 2016 at 3:46 AM Sanne Grinovero <sa...@hibernate.org> wrote:
>>
>> Hi Steve,
>> Hibernate Search doesn't customize
I'm puzzled.
There seems to be a javax.validation related issue which is failing
the integration tests running on Arquillian / WildFly for the
Hibernate Search / WildFly tests on JDK9.
http://ci.hibernate.org/view/JDK9/job/hibernate-search-master-jdk9/291/console
But more importantly.. anyone
Hi Steve,
Hibernate Search doesn't customize the loaders: if any we want to make
sure that whatever customization has been defined is being used by
Search as well.
Hibernate OGM does of course replace the default loaders; I'm not sure
how nicely that interacts with the user wanting to override it.
gt;> FailSafe version (2.19.1)?
>>
>> --Gunnar
>>
>> [1] http://openjdk.java.net/jeps/223
>> [2] https://hibernate.atlassian.net/browse/HV-1048
>>
>>
>> 2016-01-20 11:36 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>>> I'm puzzle
On 19 January 2016 at 15:25, Steve Ebersole wrote:
> I'd like to get this work into 5.1. But, as much as possible, I'd like to
> get the ProperSolution in place rather than just a
> StepInTheRightDirection. If we need to push this date 2-4 weeks I am ok
> with that. That
I would love that. We actually discussed such an approach a couple of
years ago, but the context was not to implement pagination correctly
but to improve the performance of the Hibernate Search mass-indexer (a
batch process which iterates through all entities to rebuild the
Lucene index).
We
It is documented here:
- https://developer.jboss.org/wiki/ForumsAdministrationAccess
However as you can see it's not easy to get to. You need to hop around
several security checks and get authorization from each party.
I can help with this as I already have access - if I remember the
whole
e the DB records the time-stamp info, or at least we can use the Ids.
>
> I added those progressively and when there were 40k/45k entries, the page
> was still loading.
>
> Vlad
>
> On Sat, Jan 16, 2016 at 1:25 PM, Sanne Grinovero <sa...@hibernate.org>
> wrote:
&
Hello all,
today I enabled an old build job on ci.hibernate.org named
"hibernate-orm-master-h2-infinispan8" and when it failed it
automatically sent a complaint to many, many of you.
Apologies, that was not intentional but a misconfiguration of the job.
It shouldn't happen again, or if it
out is this '5.0.7.Final' is
the same for all your libraries from Hibernate ORM, but that's easily
done with a property.
Thanks,
Sanne
>
> Thanks.
>
> 2016-01-14 16:59 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>>
>> Hi Petar,
>> Infinispan can work as
Hi Petar,
Infinispan can work as a separate service, but that's not the default.
It's primarily designed for embedded caching, is OSS, implements
JSR-107 and also has integration helpers for Spring.
There are several other OSS implementations too; AFAIR cache2k is a
good one and also implements
Could you try again now please?
On 13 January 2016 at 19:26, Steve Ebersole wrote:
> Trying to push and verify my announcement blog post for 5.0.7 release, but
> Jenkins fails to build it[1]. Apparently command `rake` not found.
>
> So what now?
>
> [1] -
+1 for Vlad's proposal to use the same JDK for tests and main code in
a given module.
Infinispan requires Java8 at runtime too, so that module should be the
only one to use Java8?
On 12 January 2016 at 07:55, Vlad Mihalcea wrote:
> I used Java 8 syntax in the User Guide
+1 this is a very common mistake for beginners.
But I'm with Hardy in not trying to shoehorn such support in our
current metadata handling, but rather to keep it in mind when moving
it all to Jandex. (how to remember that?)
On 12 January 2016 at 11:49, Hardy Ferentschik
Hi Steve,
when explicitly setting the Dialect to an empty string I have several
failures; when leaving it as-is I believe this run was valid though,
at least that's the feeling I'm getting from the kind of failures:
This is finally fixed. Had to upgrade the plugin too, let's keep an eye on
it for other possible regressions.
On 8 Jan 2016 14:56, "Gunnar Morling" <gun...@hibernate.org> wrote:
> 2016-01-08 14:39 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
> > Do you hav
Hi Alex!
I'm not expecting you to be able to work much on that 107 based
cache.. if you can that's great of course, but realistically if you
could just make it good enough for a PR then I think we should be able
to help finish that. The "extension points" we discussed can certainly
wait to be
Do you have an example of such a PR being closed?
For sure that was never our intention, but be aware that such options
can be set globally on the ci server as project detaults, but can be
overriden in a specific build task. So I'd check the build task which
did this as for example Search PRs
Since one can delete an immutable entity, and then create (insert) a
new one to replace it, from the point of view of the Cache the entry
is not immutable and needs to be treated with the usual safety and
consistency concerns.
As Radim suggests, optimizations like using a local cache might make
Hello all,
the Hibernate Search release 5.5.2.Final is now available and is
probably the best of this year:
http://staging.in.relation.to/2015/12/27/Hibernate-Search-Newyearrelease/
Special thanks to all contributors and allow me to wish the trend to
continue next year!
Sanne
Merry Christmas and happy New Year!
On 25 December 2015 at 02:42, Alex Snaps wrote:
> Merry Christmas. And wishing you all a happy & yet challenging 2016!
> On Thu, Dec 24, 2015 at 4:37 PM Gunnar Morling wrote:
>
>> Merry Christmas and a happy New
On 26 December 2015 at 16:55, Steve Ebersole wrote:
> +1 from me on the concept.
>
> Of course the problem is always the resources needed keep that going. But
> if you are offering... I huge +1 from me.
Same here :) +1
___
On 22 December 2015 at 17:34, Gunnar Morling wrote:
>> yes we could use an optional/provided dependency, but
>> that would not be "proper".
>
> That would actually be my preference; If the javax.money types are
> present, enable the required Types etc. otherwise not. It's a
ded and focused on getting the remote dialect fly. Let's
>> life out the module obsession once we actually gain something from it
>> ;)
>>
>> --Gunnar
>>
>>
>>
>> 2015-12-16 14:04 GMT+01:00 Sanne Grinovero <sa...@hibernate.org>:
>>> Hello all,
&
Thanks for the release Gail!
I did the Twitter announce; I'll leave the G+ task to someone familiar
with that.
(BTW we us twitter @Hibernate, not @hibernate-dev for announcements)
Did you have any issue with doing these?
Regarding the blog: it would be nice to mention which version was released
Hello all,
Apache Lucene 5.4.0 is released as stable, and while it includes
several benefits - not least a performance fix from myself which I'd
be keen to take advantage of - there are no significant changes
visible to end users, expect I think this one is worth a warning:
LUCENE-6590:
Hello all,
we generally have been trying to target the versions of Infinispan
provided by the WildFly version we're targeting for compatibility with
a specific OGM release cycle.
I would like to change that, and for example now switch to the latest
Infinispan 8.1.0.Final (rather than the one in
On 15 December 2015 at 01:46, Steve Ebersole <st...@hibernate.org> wrote:
> It's very possible that code comments may no longer be pertinent.
Right, that's what I'm trying to figure out. Do you remember which
possible deadlock it might have referred to?
>
> On Mon, Dec 14, 2015 at
701 - 800 of 2025 matches
Mail list logo