[
https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519088#comment-17519088
]
Steven Schlansker commented on MDEP-791:
----------------------------------------
I appreciate that this is ultimately a bug in Maven Core, however a fix there
is likely to take a long time (Maven 4?) and in the meantime users cannot
target any new JDK 17+.
Should we consider releasing artifacts that support JDK 17+ source level, but
use the old (incorrect) checker rules? At this point we are waiting for a very
long time with no progress. I agree it's a stop-gap but the whole community
that wants to target latest JDK is stuck on this set of issues at this point.
Fixing the Maven bug with dependency resolution is a great outcome, but it
should be implemented bottom-up (first fix core, then improve checker rules)
rather than the other way around (improve checker rules, break, wait
indefinitely on core...)
> Non-test scoped and transitive dependencies in compile scope
> ------------------------------------------------------------
>
> Key: MDEP-791
> URL: https://issues.apache.org/jira/browse/MDEP-791
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0, 3.3.0
> Reporter: Slawomir Jaranowski
> Priority: Critical
> Attachments: MDEP-791.zip
>
>
> When we use some dependency in test classes which is not used in production
> code but is required as transitive dependency for other used in production
> code - such dependency should not be included in {*}{{Non-test scoped}}{*}.
> Example:
> * test code use {{ObjectCodec}} from {{jackson-core}}
> * production code use only {{ObjectMapper}} from {{jackson-databind}}
> * production code don't use any classes from {{jackson-core}}
> {{jackson-core}} is needed by {{jackson-databind}} and must by in compile
> scope so should not be reported as {{Non-test scoped}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
