[
https://issues.apache.org/jira/browse/MRESOLVER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790517#comment-17790517
]
ASF GitHub Bot commented on MRESOLVER-442:
------------------------------------------
struberg commented on PR #381:
URL: https://github.com/apache/maven-resolver/pull/381#issuecomment-1829681176
My POV:
If a project has say a java8 min requirement via m-enforcer-p then every
runtime+compile dependency (minus optional deps) must adhere to this rule as
well. We can imo skipp provided, test and optional deps.
BUT: if some dependency has a multi-release-jar with *additional* support
for newer java versions, then this is also perfectly fine as long as it can
execute on the requested jvm version.
> New JDK transport JAR mixes classes with different bytecode
> -----------------------------------------------------------
>
> Key: MRESOLVER-442
> URL: https://issues.apache.org/jira/browse/MRESOLVER-442
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-3
>
>
> And hence is unusable in projects that use Enforcer to enforce highest
> allowed bytecode (like Maven is).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
