New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
j.l.ClassNotFoundException: o.a.m.s.d.t.DependencyTreeBuilderException when used with m-enforcer-p 3.0.0 #131
Comments
probably connected with #43 |
Could be. It seems the issue happens after apache/maven-enforcer@ca40308 |
Yes I'm aware about that, working on it but it take time |
Other rules like enforceBytecodeVersion fail with the same. Will update the title/summary. |
Is this commit should resolve it ... |
But current master (98f6819) + m-e-p/3.0.0 gives
|
ok, the problem is that we can try to add dependency to plugin execution with version |
That's not going to work: there can only be one version of a groupId/artifactId. |
Adding an explicit additional dependency on
However this workaround may potentially fail with another set of rules - the enforcer itself may not like it either... |
For me this is not working. I am hoping for a real fix. |
/me too on the error with maven-enforcer 3.0.0, and /me too on adding
not providing a successful work-around; with this in place, the root cause changes to Sorry! |
Same issue after upgrading to SpringBoot 2.5.3 spring-projects/spring-boot#27682 |
@pzygielo could You retest with the latest master? |
I just did with master currently pointing to d380fe5. For me, using Enforcer + extra rules from AspectJ Maven Plugin, it fixes the problem. A new release would be most welcome. Thank you very much. |
As Alexander - I confirm, d380fe5 works fine for me. Thank you. |
Freshly released m-enforcer-p 3.0.0 makes EER unusable.
Observed on
The text was updated successfully, but these errors were encountered: