[
https://issues.apache.org/jira/browse/MRESOLVER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790481#comment-17790481
]
ASF GitHub Bot commented on MRESOLVER-442:
------------------------------------------
cstamas commented on PR #381:
URL: https://github.com/apache/maven-resolver/pull/381#issuecomment-1829539620
This is the ONLY option that produces "clean" Java8 artifact usable in
downstream projects that use enforcer (like Maven is). Moreover, Maven for
example sets the bar low, is Java8, so even if I "hack" something here like you
propose, hack will need to be carried over (as hack usually pulls more hacks)
downstream to exclude Java11 JAR from enforcement etc...
So, IMO this is the best solution as:
* it works
* does not impose any "workarounds" is really just a drop-in (no hacks
needed)
* even offers downstream clients choice (it is not only Maven that consumes
this library)
> 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)
