Especially because it is hitting directly an area (type system) we are
majorly overhauling. Adding more stuff in 5.x that we need to convert
later to the new contracts is not ideal. Just thought I'd throw it out
there though to gauge interest.
On Thu, Aug 18, 2016 at 8:43 AM andrea boriero
I'm not following the 5.2 -> 6.0 piece. You mean because we merged the JPA
contracts into our version of those contracts directly? That led to very
few *real* migration problems. The only ones I know of are the once where
we had to rename the Hibernate version of a method because JPA happened
I would prefer to postpone JavaMoney/Moneta integration to 6.0.
In case this is not possible I agree with including also the CDI work.
On 17 Aug 2016 21:56, "Steve Ebersole" wrote:
> For whatever reason discussion about JavaMoney/Moneta support has heated up
> again the
On 08/17/2016 03:54 PM, Steve Ebersole wrote:
> For whatever reason discussion about JavaMoney/Moneta support has heated up
> again the past few days. Is this important enough to warrant a 5.3 release?
My (late) vote is to rename 5.2 -> 6.0 and have the 5.3 release be based
on the current ORM