for resolving the issue with the missing
pom file.
-Greg
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, January 11, 2012 3:27 AM
To: Maven Users List
Subject: Re: releasing a multi-modult project
assuming that the project
Friedenhagen [mailto:mfriedenha...@gmail.com]
Sent: Saturday, January 14, 2012 4:57 AM
To: Maven Users List
Subject: RE: releasing a multi-modult project
Just guessing: One important thing: the branch given in
//project/scm/connection *must* match the checked out workspace. So using
Subversion when
assuming that the project that succeeds is the aggregator root, everything
is fine. prepare runs on the aggregator root and tags from that root. just
run perform and it will check out all the modules and release them.
if it is not the aggregator root, you may have to release each scm root
To: Maven Users List
Subject: Re: releasing a multi-modult project
assuming that the project that succeeds is the aggregator root,
everything is fine. prepare runs on the aggregator root and tags from
that root. just run perform and it will check out all the modules and
release them
I inherited a multi-module project from someone that is no-longer with
the company. I have Maven experience, but not with multi-module
projects. Release prepare is succeeding for the first module, and is
skipping the remainder of the modules. How do I get release prepare to
prepare all modules?
