-
Notifications
You must be signed in to change notification settings - Fork 127
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
Upgrade to Maven 3 APIs and Aether #326
Comments
…ncy resolution
…ncy resolution
…ncy resolution
…ncy resolution
Fix #326 Migrate to using Maven 3 APIs and Aether for dependency resolution
Is the exact Maven Version "3.5.4" really needed? |
@brabenetz See #327. It's possible the plugin may work with 3.5.2. Oldest version tested was 3.5.4 through this repo's Travis setup. It's odd that yours is using an older Maven. You could try reducing the version to 3.5.2 and see if the tests pass on version 3.5.2? Alternatively you can upgrade Maven as part of your build, see https://github.com/apache/storm/blob/38b09fd229d2034a0fb6d5359eaa0b8ecdc0b61a/.travis.yml#L46 |
@srdo I will just wait until travis-ci updates there images, and update the license-maven-plugin later. |
It would be good to upgrade to Maven 3 APIs and Aether. It is difficult to implement some features (programmatic dependency resolution for instance) correctly with the old APIs, and they are also deprecated in newer Maven versions.
The plugin could be upgraded to use Maven 3 dependencies, and maven-resolver (Aether).
The text was updated successfully, but these errors were encountered: