Re: cdi-api leaking?

Perfect, thanks a lot for the help. Let me know if I can support him - even if I guess you are already doing it ;). Le mer. 9 déc. 2020 à 21:02, Michael Osipov a écrit : > Am 2020-12-09 um 11:39 schrieb Romain Manni-Bucau: > > Any issue moving forward on https://github.com/apache/maven/pull/408

Re: cdi-api leaking?

Am 2020-12-09 um 11:39 schrieb Romain Manni-Bucau: Any issue moving forward on https://github.com/apache/maven/pull/408 ? No issue, I have delegated the IT to a former colleague who is looking for simple issues to contribute. Turning your test case into an IT seems like a perfect fit. M R

Re: cdi-api leaking?

+1 for dropping. Also already had problems with it. LieGrue, strub > Am 01.12.2020 um 17:50 schrieb Romain Manni-Bucau : > > Up, > > Encountered a few bugs related to this regression, wonder how we want to > tackle it. > My 2cts would be to drop cdi-api and replace the single used > annotation

Re: cdi-api leaking?

I'm missing an integration-test that confirms the need for this, otherwise I expect this discussion might pop up again every several years. Just ensure it breaks if the exported packages are activated again for clear reasons. Robert On 9-12-2020 11:39:35, Romain Manni-Bucau wrote: Any issue mo

Re: cdi-api leaking?

Any issue moving forward on https://github.com/apache/maven/pull/408 ? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn