[
https://issues.apache.org/jira/browse/MNG-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243923#comment-17243923
]
Romain Manni-Bucau commented on MNG-7045:
-----------------------------------------
[~michael-o] well, if it is a prerequisite to merge I'll do but it is not CDI
specific, this is why Mark said maven shouldn't leak any library except
org.apache.maven (or its core backbone) so it is kind of already tested with
exportedpackage tests, here the configuration was just wrong. This is why I
didn't add a test. Let me know if I must add one or if we are fine with our
current coverage.
side note: same issue applies to jsr250 but since it didnt move we don't hit it
as easily ;)
> Drop CDI API from Maven
> -----------------------
>
> Key: MNG-7045
> URL: https://issues.apache.org/jira/browse/MNG-7045
> Project: Maven
> Issue Type: Bug
> Components: core
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> This is an old leak which triggered a lot of regressions and still triggers
> bugs in mojos.
> Since there is on real justification in maven itself (@Typed is not since
> there are alternative and cdi is not used in any piece of maven), let's drop
> it.
> If a plugin needs it, it already has it since cdi-api is outdated anyway.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
