If you really want to get fancy, this is also possible. Only this
requires a little more hacking.
Take a look at [1] which checks the dependencies, especially line 171 to
174.
prompter.showMessage(
"This project relies on a SNAPSHOT
of the release plugin. This may be necessary during testing." );
result = prompter.prompt( "Do you want
to continue with the release?",
Arrays.asList(
new String[]{"yes", "no"} ), "no" );
If you incorporate something like this on lines 231 and 232 it is the
brute way. You accept all snapshots or not. If you like something even
more fancy ;) you can incorporate it at the checkArtifact method on line
261 you can even fine tune it, so it will ask for each snapshot found.
Do the same with the versions as I explained in the other mail and
you're set. If you even introduce a variable to turn this on and off,
maybe it can make it into the official build.
Hth,
Nick Stolwijk
[1]
http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/CheckDependencySnapshotsPhase.java
Matthew McCullough wrote:
Thanks for the workaround. You are right -- that could get really tedious in
following the thread of SNAPSHOTs. I will give it a try. But I really wish
there were an option to flat out "override" the release plugin to
acknowledge "I'm doing something really dangerous but let me do it
anyway"...
-Matthew
Steven Rowe wrote:
Hi Matthew,
I have gotten around this problem by deploying the SNAPSHOT projects in
question to an internal repository, after first renaming their versions
from X.X.X-SNAPSHOT to X.X.X-myco-X (or something similar). This can
get messy, since SNAPSHOTs sometimes depend on other SNAPSHOTs, and
those have to also be fixed in the respective POMs. But it works. And
it's worth it - maven-release-plugin rocks!
Steve
Matthew McCullough wrote:
Mavenites,
I have a project in which we depend on SNAPSHOTs. Unfortunately, three
of
them are not actively being developed at the moment, however we still
have
to use them. I realize it is a very bad practice to depend on these
since
you never know what is going to be changed. However, is there any way I
can
override release:prepare from FORCING me to have all dependencies as
non-snapshots?
I've reviewed all the documentation I can find on:
http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html
and cannot find anything that seems to allow overriding this behavior of
requiring all concrete version numbers for dependencies.
Thanks for any pointers.
Matthew McCullough
Ambient Ideas, LLC
[EMAIL PROTECTED]
www.ambientideas.com
---------------------------------------------------------------------
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]
