I've been using mvn for some time now. However my nice smooth release
procedure has just broken - I can't figure out if it's something I've
done myself or something that's changed in a plug-in.
I have a parent pom. That has sub modules. The first is a library that
all the others require. All 4 modules declare the parent as the pom
parent.
When I do a "mvn install", it correctly :
(a) installs the parent pom into local repository,
(b) builds & installs the common library (which depends on the parent
pom) into local repository
(c) then goes onto the other modules (which depend on both the parent
pom and the common library).
This was working for "release:prepare" and "release:perform" too.
However now the "release:perform" fails. The common library has not been
installed, so building the first of the other dependant modules fails.
I've tried adding the following to the parent pom, but it didn't help.
<plugin>
<artifactId>maven-release-plugin</artifactId>
<inherited>true</inherited>
<configuration>
<preparationGoals>clean install</preparationGoals>
</configuration>
</plugin>
Any help appreciated.
Thanks, Ian Orford.
--------------------------------------------------------------------------------
The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient, please
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to
http://www.dresdnerkleinwort.com/disc/email/ or contact the sender.
--------------------------------------------------------------------------------
