Personally I would like to see a new Git branch with CDI 2.0 and the integration test results on Jenkins. This would give us more confidence. Question: Does the CDI 2.0 have any NEW mandatory descriptive methods without default value already introduced in OLD annotations CDI 1.0/1.1?
On Tue, Feb 6, 2018 at 8:57 AM, Romain Manni-Bucau <[email protected]> wrote: > > For the reproducer here it is https://github.com/ > rmannibucau/test-maven-plugin - pretty trivial you'll see ;). > > 2018-02-06 8:05 GMT+01:00 Tibor Digana <[email protected]>: > >> Changing the package would not be possible in 3.x. >> > > Why? In particular since it is an old regression already reported on the > list due to guice introduction it shouldn't be delayed for this kind of > reason IMHO. > Was less visible until CDI 2 was released cause the API difference was not > triggered but now there are new entries it breaks immediately. > > >> Guessing the version 4.0.0. >> WDYT? >> > > Would stay a blocker until 4 is out which is that soon so not sure it is > an option. > > >> >> On Tue, Feb 6, 2018 at 8:01 AM, Tibor Digana <[email protected]> >> wrote: >> >>> The question is maybe about what is realistic for Maven devs. >>> Shading the CPI package (to something like org.apache.maven.cdi.*) would >>> be maybe the case instead of removing the original CDI and reinventing the >>> wheel. >>> >>> On Tue, Feb 6, 2018 at 7:52 AM, Hervé BOUTEMY <[email protected]> >>> wrote: >>> >>>> and does the MNG issue contain a reproducible test case for us to >>>> investigate >>>> more precisely? >>>> >>>> Regards, >>>> >>>> Hervé >>>> >>>> Le lundi 5 février 2018, 22:11:56 CET Robert Scholte a écrit : >>>> > Is there a MNG[1] issue? >>>> > >>>> > Robert >>>> > >>>> > [1] https://issues.apache.org/jira/browse/MNG >>>> > >>>> > On Sat, 03 Feb 2018 16:29:49 +0100, Romain Manni-Bucau >>>> > >>>> > <[email protected]> wrote: >>>> > > Up? >>>> > > >>>> > > Le 19 janv. 2018 13:18, "Romain Manni-Bucau" <[email protected]> >>>> a >>>> > > >>>> > > écrit : >>>> > >> Hi guys, >>>> > >> >>>> > >> cdi-api is still in maven lib and breaks any plugin using it since >>>> it is >>>> > >> an old version, can it be dropped or at least isolated from plugin >>>> > >> classloaders? >>>> > >> >>>> > >> Thanks, >>>> > >> Romain Manni-Bucau >>>> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>> > >> <https://rmannibucau.metawerx.net/> | Old Blog >>>> > >> <http://rmannibucau.wordpress.com> | Github >>>> > >> <https://github.com/rmannibucau> | LinkedIn >>>> > >> <https://www.linkedin.com/in/rmannibucau> >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: [email protected] >>>> > For additional commands, e-mail: [email protected] >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >> >
