You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try to use v0.1.0 of this plugin on an older version of Maven, you will experience symptoms similar to those described in jeremylong/DependencyCheck#1054.
v0.0.6 continues to work fine.
I had upgraded this after reviewing the output of mvn versions:display-plugin-updates; while some new plugin versions specified that they would require a minimum of e.g. 3.5.4, this one did not:
[INFO] The following plugin updates are available:
[INFO] org.honton.chas:exists-maven-plugin ................ 0.0.6 -> 0.1.0
[INFO]
[INFO] Project inherits minimum Maven version as: 3.3.9
[INFO] Plugins require minimum Maven version of: 3.3.9
[INFO]
[INFO] Require Maven 3.5.4 to use the following plugin updates:
[INFO] org.codehaus.mojo:license-maven-plugin .............. 1.20 -> 2.0.0
Perhaps you could ensure that the published plugin compatibility is accurate, to avoid other people encountering the same issue?
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the report.
I've updated the readme to indicate minimum required versions.
Next release will enforce the minimum required versions for java and maven.
Sounds reasonable to me. Since changing and republishing artifacts is generally a Bad Thing, I can't ask for more so I think we can consider this issue closed.
If you try to use v0.1.0 of this plugin on an older version of Maven, you will experience symptoms similar to those described in jeremylong/DependencyCheck#1054.
v0.0.6 continues to work fine.
I had upgraded this after reviewing the output of
mvn versions:display-plugin-updates
; while some new plugin versions specified that they would require a minimum of e.g. 3.5.4, this one did not:Perhaps you could ensure that the published plugin compatibility is accurate, to avoid other people encountering the same issue?
Thanks!
The text was updated successfully, but these errors were encountered: