Open dkirrane opened 7 years ago
Here's what I've tried commit fd9436d9
Line 228 I'm setting the version of the dependencies to a non existing version dependency.setVersion("fooBar");
and the pom.xml.new-version
gets updated correctly
However, the mvn clean install
doesn't fail.
Is there a way to tell MavenLifecycle to reload dependencies after the pom file is written back
Take a look a the versions-maven-plugin, as that has support already for updating properties (which you might be able to use for this case)
On Thu, Dec 1, 2016 at 2:06 PM, dkirrane notifications@github.com wrote:
Here's what I've tried commit fd9436d9 https://github.com/dkirrane/maven-external-version/commit/fd9436d91939288db5fdf69c05a6ca4c3d8a8f57
Line 228 I'm seeting the version of dependency to a non existing version dependency.setVersion("fooBar"); However, the mvn clean install doesn't fail.
Is there a way to tell MavenLifecycle to reload dependecies after the pom file is written back
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bdemers/maven-external-version/issues/4#issuecomment-264263123, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGGcrcq0PYUiPY0qqvTE-gInaK2lL5Fks5rDxqogaJpZM4LBwpY .
In my case I'd like to update certain dependencies in the poms during the build i.e. to also use
-Dexternal.version=1.0-featureX