I don't think any current version of Maven 2.0.x recognises attached
artifacts in the reactor, so since one has been added to the build,
you'll need to change the preparation goals to "clean install".
Cheers,
Brett
On 12/05/2008, at 6:25 AM, Dennis Lundberg wrote:
Hi all
After about a gaz
Hi all
After about a gazillion attempts I was finally able to get 'mvn
release:prepare' to actually check in the changed POMs.
For some reason release:prepare fails because one of the artifacts being
release is not available in any repo, which it shouldn't be yet - I'm
only preparing the rel
