plug-in and SNAPSHOT dependencies
The advice generally given in these kinds of situations is that you
create a "release" of the offending artifact either with your own fake
non-snapshot version or under your own groupId with a non-snapshot
version.
So in this case, I would probably create
The advice generally given in these kinds of situations is that you
create a "release" of the offending artifact either with your own fake
non-snapshot version or under your own groupId with a non-snapshot
version.
So in this case, I would probably create a release of the stat-scm
plugin with ver
We are using the Maven 2 release plug-in for our release process.
The plug-in checks for SNAPSHOT dependencies and refuses to proceed in
case it finds a SNAPSHOT dependency. This makes perfectly sense and is
what is desired.
What I do not understand is the fact that it also checks in my report
