Open ateglas opened 1 year ago
I think most people want controlled upgrade. Is there any way of locking the version after this change?
One of the ways to do it, which works for both upgrading and downgrading, would be to overwrite the versions for the dependent libraries. It is just that now, gradle plugin users get, by default, the latest bugfixes and the latest parsers, while maven plugin users get, by default, just the parsers that were available in the included versions.
<plugin>
<groupId>se.bjurr.violations</groupId>
<artifactId>violation-comments-to-gitlab-maven-plugin</artifactId>
<version>1.47.0</version>
<dependencies>
<dependency>
<groupId>se.bjurr.violations</groupId>
<artifactId>violation-comments-to-gitlab-lib</artifactId>
<version>1.87.0</version>
</dependency>
<dependency>
<groupId>se.bjurr.violations</groupId>
<artifactId>violations-lib</artifactId>
<version>1.156.3</version>
</dependency>
</dependencies>
...
</plugin>
@tomasbjerre @ateglas can you please review PR https://github.com/tomasbjerre/violation-comments-to-gitlab-maven-plugin/pull/11
Would it be possible to update the dependencies for the maven plugin so that it requests for the latest versions of violation-comments-lib and violation-lib? The gradle plugin for example requires a range, anything 1.+
Basically, replace:
with either
or just with latest version hardcoded