[
https://issues.apache.org/jira/browse/MNG-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243811#comment-17243811
]
Romain Manni-Bucau commented on MNG-7045:
-----------------------------------------
[~michael-o] tomee, meecrowave, weld, camel-cdi, quarkus in some
context/config, exec-maven-plugin in java mode, all will fail to use CDI 2 API
properly (Instance will not have stream() support for example since it was not
in 1.1). Indeed upgrading to cdi-api 2.0 is a workaround in maven but since
maven does NOT need this dependency and it creates issue with all
implementation there is no point to try to keep it. This always had been a bug
and was reported years ago, we were just too slow to fix it - blame me because
I guess I was one of the first to face it. Indeed some applications not using
overlapping features will run properly but this is still a bug. Also leaking
API not provided is another bug (why do we export javax.enterprise and not use
it at all except @Typed from memory which is not even needed. Indeed if you
have another fix i'm fine with it but I think it is the simplest and less
breaking fix to that old bug.
> 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)
