Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

I'm happy to see all the progress on this while I've been occupied with 5.1.13 and some other urgent issues. I hope to have time to get caught up on things later today or tomorrow. On Thu, Mar 22, 2018 at 10:55 AM, Gunnar Morling wrote: > I've mostly used Japicmp recently

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

On Thu, Mar 22, 2018 at 4:20 PM, Sanne Grinovero wrote: > To make sure all the noise form "false positives" won't get us to miss > something, someone knows an alternative tool which can do better? > We use this one for HV https://github.com/siom79/japicmp . Not sure it's

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

I just pushed the first round of fixes for this upstream. On Thu, Mar 22, 2018 at 11:00 AM Sanne Grinovero wrote: > On 22 March 2018 at 15:55, David Lloyd wrote: > > This tool is usually pretty good; in fact I think it likely that it's > > the best

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

On 22 March 2018 at 15:55, David Lloyd wrote: > This tool is usually pretty good; in fact I think it likely that it's > the best of its kind. The false positives are really a fairly recent > development AFAIK; I don't recall hitting any when I ran it for our > EJB changes

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

On 22 March 2018 at 15:36, Emmanuel Bernard wrote: > As we discussed on the phone, I am skeptical of the custom HSearch backend > for it: > - it would be the only database doing that > - it’s a lot of work that would probably be best spent improving the > Infinispan remote

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

This tool is usually pretty good; in fact I think it likely that it's the best of its kind. The false positives are really a fairly recent development AFAIK; I don't recall hitting any when I ran it for our EJB changes a year or two ago. It might be a good idea to contribute a fix for the

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

I don’t think spending the n hours on outweighs the explained benefits so I would keep it that way. The reason I had the dates were because blogs are time sensitive (like any content really), and it avoids or reduces the risk of slug collision for which we would need to implement a workaround

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

Not sure. animal-sniffer is the other one I know, but not sure it would be better. On Thu, Mar 22, 2018 at 10:21 AM Sanne Grinovero wrote: > To make sure all the noise form "false positives" won't get us to miss > something, someone knows an alternative tool which can do

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

As we discussed on the phone, I am skeptical of the custom HSearch backend for it: - it would be the only database doing that - it’s a lot of work that would probably be best spent improving the Infinispan remote query FT APIs - once there it will be a maintenance burden. Emmanuel > On 22 Mar

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

To make sure all the noise form "false positives" won't get us to miss something, someone knows an alternative tool which can do better? Thanks, Sanne On 22 March 2018 at 14:22, Steve Ebersole wrote: > Yes there were "lots of differences" but a vast majority of them are >

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

Related with the TypeConfiguration and BootstrapContext work, I have just made a PR targeting your last comments, but I need to know if the work done it's fine and especially if it is enough to be considered done and then integrated. On 22 March 2018 at 14:15, Steve Ebersole

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

On Thu, Mar 22, 2018 at 2:39 PM, Gunnar Morling wrote: > Note I'm not suggesting to change any existing URLs. Rather my question is, > should we go to the date-less schema for new posts going forward. > Personally I like having the date information in the URL but I won't

Re: [hibernate-dev] API differences in Hibernate ORM 5.1 vs 5.3

Yes there were "lots of differences" but a vast majority of them are false-positives, not just those listed in the already massive "false positives" section. I've been going through the non-"false positive" section and "resolving" specific items (via strike-through) with either (1) link to Jira

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

Still waiting for feedback on the PR or Jira. I will integrate upstream today if I don't hear replies needing changes But regardless, this is not the only change CR2 is waiting on as I mentioned before On Thu, Mar 22, 2018, 8:54 AM Sanne Grinovero wrote: > Could you help

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

Could you help us understand. None of the SPI changes have been merged in master yet? On 22 March 2018 at 13:39, Steve Ebersole wrote: > Then you'll have to wait. Seems like snapshot is better than waiting but of > course your opinion seems just waiting is better... > > On

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

No, snapshots are confusing when you need multiple people to collaborate on a POC. It's not clear if a patch will work the same to others and it's unpractical to match to a specific source commit. Why would we ever publish CRs if SNAPSHOTS are the same. On Thu, 22 Mar 2018, 13:17 Steve

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

Like a snapshot? On Thu, Mar 22, 2018, 7:22 AM Sanne Grinovero wrote: > On 22 March 2018 at 12:18, Steve Ebersole wrote: > > There is already a branch that contains these changes that they can work > > with... no need to wait for a CR. I still want to

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

By the way, if some articles are more technical and we put some effort in keeping them up-to-date, we could put them in a separate section and just post in the blog about their existence and updates. Davide On Thu, Mar 22, 2018 at 1:14 PM, Davide D'Alto wrote: >> I

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

> I personally don't see the problem with dates in URLs. I don't see any > problem with not having them, either. But I do see a problem with changing > the URL scheme: potential dead links, SEO nightmare... We would need a damn > good reason to do it, and I'm not sure those you mentioned are

Re: [hibernate-dev] Defaultable service strategies

+1 Makes sense to me. On 03/21/2018 02:42 PM, Steve Ebersole wrote: > Thoughts on allowing certain services to be defaulted to the single > implementor registered with the `StrategySelector` service when there is > just one? > > For example, when resolving the RegionFactory unless both (a) >

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

I also switched my blog from dates to simple slugs at the beginning of the year. As long as you add the proper Redirection rules in .htaccess_posts, it shouldn't be any problem. Google does not penalize 301 redirects, so you don't lose any SEO ranking if you use 301 redirects. We can also

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

> The data in the post slug only makes sense for news sites where posts are highly associated to a given date. A lot of our posts are. Release announcements and weekly newsletters in particular. I personally don't see the problem with dates in URLs. I don't see any problem with not having them,

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

On 22 March 2018 at 12:18, Steve Ebersole wrote: > There is already a branch that contains these changes that they can work > with... no need to wait for a CR. I still want to let Andrea finish the > work on TypeConfiguration and BootstrapContext before we cut CR2. It would

Re: [hibernate-dev] Hibernate ORM 5.3 CR2 ?

There is already a branch that contains these changes that they can work with... no need to wait for a CR. I still want to let Andrea finish the work on TypeConfiguration and BootstrapContext before we cut CR2. On Thu, Mar 22, 2018 at 7:17 AM Sanne Grinovero wrote: >

[hibernate-dev] Hibernate ORM 5.3 CR2 ?

Steve, all, would it be possible to tag a CR2 as soon as the Caching SPI changes are complete? That would help the Infinispan team so they can get started immediately on their side of things. Thanks, Sanne ___ hibernate-dev mailing list

Re: [hibernate-dev] Starting 5.2.16 release

That's an interesting idea, especially as these messages like "please don't push" are highlighting the current process is fragile. Personally I quite like the fact that I can see the previous tags in my history during development but I guess it's just a habit. What do others think? On 22 March

Re: [hibernate-dev] Starting 5.2.16 release

I was thinking to propose this part of the release process gets changed a bit, so that the commit of a "Final" version never goes into "master", but remains on a tag. Something like this: # detach head git checkout # edit file and change hibernateVersion editor gradle/base-information.gradle #

[hibernate-dev] Starting 5.2.16 release

*Please do not push anything to 5.2 branch.Thanks,Andrea* ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Why do we have the date in the URL of blog posts?

Hi, The data in the post slug only makes sense for news sites where posts are highly associated to a given date. In our case, the data works against us as people might think an article is outdated by just inspecting the slug and thinking that a 3 year-old article might not be relevant anymore.

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

On 22 March 2018 at 07:41, Emmanuel Bernard wrote: > > On 20 Mar 2018, at 12:41, Sanne Grinovero wrote: > > > > On 20 March 2018 at 10:50, Emmanuel Bernard wrote: >> >> I think treating the client side HSearch input and

[hibernate-dev] Why do we have the date in the URL of blog posts?

Hi, While talking to a few bloggers from the Java ecosphere at JavaLand last week, the question came up why we have the date in the URL of blog posts. Arguably, it doesn't add value there (we show the date on the actual posts themselves), and makes the URLs slightly worse to read. In particular,

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

> On 20 Mar 2018, at 12:41, Sanne Grinovero wrote: > > > > On 20 March 2018 at 10:50, Emmanuel Bernard > wrote: > I think treating the client side HSearch input and transparently push it > down is a recipe for

Re: [hibernate-dev] [HV] Retiring HibernateValidatorContext#parameterNameProvider()

> On 20 Mar 2018, at 13:24, Guillaume Smet wrote: > > Maybe we could have some gain by avoiding the parameter name generation in > most cases but I'm not sure it's worth making the code less readable. Readability is the root of all evil. I read that somewhere on the

Re: [hibernate-dev] Async JDBC proposal

Slides 8 explicitly says that it is not built on JDBC, is not a replacement but will live alongside. > On 20 Mar 2018, at 22:17, Mark Rotteveel wrote: > > The slides shown are from last year. Somehow that blog still promotes > that ADBA is somehow a replacement of JDBC,

Re: [hibernate-dev] Async JDBC proposal

Yep correct link, sorry about that :/ https://blogs.oracle.com/java/jdbc-next%3a-a-new-asynchronous-api-for-connecting-to-a-database > On 20 Mar 2018, at 12:13, Radim Vansa wrote: