[
https://issues.apache.org/jira/browse/MRESOLVER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790499#comment-17790499
]
ASF GitHub Bot commented on MRESOLVER-442:
------------------------------------------
cstamas commented on PR #381:
URL: https://github.com/apache/maven-resolver/pull/381#issuecomment-1829598101
Unsure which "enforcer bug" you refer to... all it does when you ask
enforcer "I don't want any higher bytecode on classpath than Java8" is to fail
when it encounters Java11 bytecode with your solution, as it really *does*
contain Java11 classes on Java 8 classpath. So, unsure where the bug is?
It does work, as PR shows. Can you show me example where it does not work?
As I said above, if JAR is Java11 and you want to use it downstream in
project that declares itself java 8, it is "enforcer bug" according to you,
that enforcer fails the build in this case?
For this no hacks (as those are like static electricity, the more you have
of those, the more you need downstream) and "bugs" needed, it just works.
> 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)
