On 28 September 2017 at 13:30, Steve Ebersole <[email protected]> wrote: > Do y'all really think it makes sense to have JPA versions in this ORM > "compatibility matrix"?
I think it's useful. Try booting a recent ORM version with an out of date JPA api jar: you'll get really weird exceptions and it's hard to figure out what's wrong. https://forum.hibernate.org/viewtopic.php?f=1&t=1043938 Hopefully in future having a single JPA API distribution (in terms of Maven coordinates) would make such issues a thing of the past, but it's going to take a while yet. > > My concern is that it is more involved (as we then try to convey in the > section below that matrix) than a cell in a matrix/table with just a > version number. > > If we end up treating JPA compatibility differently (removing from table) > then the table is just made up of "Java compatibility", which we can > probably illustrate simpler than a single vertical row of versions. > > On Thu, Sep 28, 2017 at 6:37 AM Guillaume Smet <[email protected]> > wrote: > >> On Thu, Sep 28, 2017 at 9:21 AM, Guillaume Smet <[email protected]> >> wrote: >> >> > I was talking about the ability to access the old series when they are >> not >> > displayed in the overview. >> > >> > AFAICS, this is definitely missing and we would need either a page with >> > all the series linked from the overview page or a button displaying the >> > retired series. >> > >> >> Done: I added a See older series button to the Releases / Overview page and >> to the Documentation page. >> >> -- >> Guillaume >> _______________________________________________ >> hibernate-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ > hibernate-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/hibernate-dev
