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 version 0.9.0 or something and specify that version in my pom. This assumes of course that no 0.9.0 version is ever expected to be released by the "official" provider of the stat-scm plugin. Then when the official 1.0.0 release is available, you can start using it instead by simply changing the version specified in the pom. But in the meantime, you can cut releases of your own projects with this fake non-snapshot build. Wayne On 4/1/07, Andreas Guther <[EMAIL PROTECTED]> wrote:
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 reporting section and if it finds there a SNAPSHOT dependency it applies the same rule. The reporting is not needed or used for a release. My problem is that we are using the stat-scm plug-in for our reports which is not available as a full version, only as a SNAPSHOT. Is there a way to tell the release plug-in to ignore specific profiles or for example the reporting section for its SNAPSHOT dependency checks? Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
