[
https://issues.apache.org/jira/browse/MRESOLVER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790580#comment-17790580
]
ASF GitHub Bot commented on MRESOLVER-442:
------------------------------------------
rmannibucau commented on PR #381:
URL: https://github.com/apache/maven-resolver/pull/381#issuecomment-1829884012
@struberg yep. Agree it needs some tuning of m-enforcer-plugin but isnt it
the case anyway?
Also is it that much used (have to admit I abandonned it years ago cause it
had too much false positives for me and the cost to tune it was way too high
for what it was bringing - validating the bytecode version is almost useless if
you have tests with acceptable coverage for ex)?
> 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)
