Hmm, looks like I might have been mistaken about the "external Hibernate
Maven plugin". The only one I can find (cannot remember if this is the one
I was thinking of) just does schema export.
On Fri, Nov 13, 2015 at 8:11 AM Steve Ebersole <steve(a)hibernate.org> wrote:
For runtime enhancement there is no change, we manage it
internally.
For build-time, legacy enhancement only offered an Ant task (there is a
Maven plugin developed by another group; I will reach out to them about
this). At the moment those folks would need to point to a new Ant task. We
could potentially simply have the "old Ant task" call the new enhancement.
The new enhancement is supported for build-time via Ant, Maven and
Gradle. The Maven and Gradle support are new to that new enhancement, so no
real changes there
On Fri, Nov 13, 2015, 1:47 AM Gunnar Morling <gunnar(a)hibernate.org> wrote:
> Hey,
>
> How would migration for a user look like?
>
> Do they need to configure a different Ant/Gradle/Maven task? Would 5.1
> (assuming the old enhancer has been removed) be able to work with
> entities enhanced by the old one, or would a re-build of the app be
> required? Would they see a deprecation at all in their IDE (do they
> interact with any classes related to enhancement directly at all)?
>
> Just trying to figure how painless migration for users to the new
> enhancer would be and whether 5.1 or possibly 6 would be the best time
> to remove the old approach.
>
> Thanks,
>
> --Gunnar
>
>
> 2015-11-12 17:46 GMT+01:00 Sanne Grinovero <sanne(a)hibernate.org>:
> > +1
> >
> > On 12 November 2015 at 16:39, Steve Ebersole <steve(a)hibernate.org>
> wrote:
> >>
https://hibernate.atlassian.net/browse/HHH-10280
> >>
https://hibernate.atlassian.net/browse/HHH-10281
> >>
> >> On Wed, Nov 11, 2015 at 12:15 PM andrea boriero <dreborier(a)gmail.com>
> wrote:
> >>
> >>> no objections
> >>>
> >>> On 11 November 2015 at 17:55, Steve Ebersole
<steve(a)hibernate.org>
> wrote:
> >>>
> >>>> I'd like to more formally deprecate the legacy bytecode
enhancement
> >>>> starting in 5.0.4 and remove it in 5.1.
> >>>>
> >>>> The new code is superior and already feature compatible back to 5.0
> Final.
> >>>>
> >>>> Any objections?
> >>>> _______________________________________________
> >>>> hibernate-dev mailing list
> >>>> hibernate-dev(a)lists.jboss.org
> >>>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>>
> >>>
> >>>
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev(a)lists.jboss.org
> >>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>