[
https://issues.apache.org/jira/browse/MENFORCER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460862#comment-17460862
]
David Pilato edited comment on MENFORCER-407 at 12/16/21, 4:44 PM:
-------------------------------------------------------------------
So you are saying that with Maven 3.8.4 and Enforcer 3.0.0 we are failing on
provided deps where with Maven 3.8.4 and Enforcer 3.0.0-M3, we don't fail and
with Maven 3.5.3 and Enforcer 3.0.0, we don't fail either.
If this is expected, then let's close the issue.
I'm super surprised by this change in the behavior though.
I believe that previously when an artifact was not found, it was simply ignored.
was (Author: dadoonet):
So you are saying that with Maven 3.8.4 and Enforcer 3.0.0 we are failing on
provided deps where with Maven 3.8.4 and Enforcer 3.0.0-M3, we don't fail and
with Maven 3.5.3 and Enforcer 3.0.0, we don't fail either.
If this is expected, then let's close the issue.
I'm super surprised by this change in the behavior though.
> Enforcer 3.0.0 breaks with Maven 3.8.4
> --------------------------------------
>
> Key: MENFORCER-407
> URL: https://issues.apache.org/jira/browse/MENFORCER-407
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 3.0.0
> Reporter: David Pilato
> Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: enforcer-3.0.0.log, enforcer.3.0.0-M3.log
>
>
> Here is the situation. I'm trying to [upgrade enforcer from 3.0.0-M3 to
> 3.0.0|https://github.com/dadoonet/fscrawler/pull/1214].
>
> Everything worked well on my laptop with Maven 3.5.3. So I looked at the
> version used by Github actions and saw that it's using Maven 3.8.4.
> As soon as I upgraded my local version of Maven to 3.8.4, I started to hit
> the same exact issue. It seems to try to pull
> net.sf.ehcache:sizeof-agent:1.0.1.
> If I revert Enforcer to 3.0.0-M3 with Maven 3.8.4, I can run without any
> issue mvn enforcer:enforce.
> So I suspect that the combination of both upgrades is triggering something.
> I noted also that 3.0.0 now tries to enforce as well dependencies marked as
> provided. Might be the reason of this.
> I attached the full logs when running with 3.0.0 and 3.0.0-M3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
