M2: problem compiling release from parent directory

["Orford, Ian" <Ia...@dresdnerkleinwort.com>]

My project has a parent pom, in which all common settings are stored, and 4
modules. 
One of the modules is a library used by the other three. 
We want the versions to be consistent across all modules. 
This is all working fine. I can install and deploy without problem.

However, when I release, I get problems.

Preparing the release with "mvn release:prepare" from the top-level
directory works fine.

When I then do a "mvn release:perform" from the top level directory, I get a
"target/checkout" directory into which all the code is extracted. Then the
build fails because the directory "target/checkout/target" doesn't exist.

The entire build works if I quickly make the target/checkout/target
directory during or straight after the checkout.

Questions
(a) Have I done something fundamentally wrong that has confused maven so
that it cant create the target sub directory?
(b) If not, how can I attach a (presumably ant) task to a phase so that it
manually creates the directory. Which phase would be best?


Many 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. 
--------------------------------------------------------------------------------