Two options:
1. change your build so that it will work with "clean verify" whenyour
local repository has been blown away. Typically this is because you
are using goals like dependency:copy and not
dependency:copy-dependencies
2. change the preparation goals in the release plugin to "clean install".
#2 is a hack, but may be necessary. In the long run #1 is to be preferred.
-Stephen
2009/11/19 Peter Niederwieser <pnied...@gmail.com>:
>
> In my multi-module project, I have a Maven plugin A and a module B that uses
> version ${project.version} of A (all modules have the same version number).
> release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
> while processing B because it cannot find version 0.3 of A. Any ideas how to
> solve this problem?
>
> Cheers,
> Peter
> --
> View this message in context:
> http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
