Skip to content
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

Declaration of <newVersion/> and <oldVersion/> should be optional #129

Closed
siom79 opened this issue Mar 22, 2016 · 1 comment
Closed

Declaration of <newVersion/> and <oldVersion/> should be optional #129

siom79 opened this issue Mar 22, 2016 · 1 comment

Comments

@siom79
Copy link
Owner

siom79 commented Mar 22, 2016

The maven plugin should be able to automatically determine and resolve the new and old version.

The new version can be retrieved from MavenProject.getArtifact() while the old version can be computed using a VersionRange query.

This circumvents problems with the ${project.packaging} variable when declaring the maven plugin in the top level pom.xml. For the packaging type maven-plugin the artifact's file type is jar and not maven-plugin as the value of ${project.packaging} would suggest.

@siom79
Copy link
Owner Author

siom79 commented May 14, 2016

Implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant