Thank you for your reply. I discovered the problem, I did not specify the version of the maven-site-plugin and it defaulted to an older incompatible version. I am using maven 3.0.3 which probably contributed to the incompatability.
Regards GB -----Original Message----- From: Mirko Friedenhagen [mailto:[email protected]] 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 development happens in trunk and you have a release branch, you have to specify the release branch in the pom. Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Jan 11, 2012 6:42 PM, "Greg Babcock" < [email protected]> wrote: > Thank you Stephen, > > The aggregator root is the project being that succeeds. I was > suspicious about release:prepare because release:perform is failing > with an error message that it can't find the pom for the aggregator > root in target directory. The target directory is not getting created > by release:perform which made me suspicious that it wasn't really passing. > > > Does anyone have any sugestions for resolving the issue with the > missing pom file. > > -Greg > > -----Original Message----- > From: Stephen Connolly [mailto:[email protected]] > Sent: Wednesday, January 11, 2012 3:27 AM > 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. > > if it is not the aggregator root, you may have to release each scm > root separately. > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random > nonsense words and other nonsense are a direct result of using swype > to type on the screen On 11 Jan 2012 00:02, "Greg Babcock" > <[email protected]> > wrote: > > > 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? > > > > > > > > NFO] > > -------------------------------------------------------------------- > > -- > > -- > > > > [INFO] Reactor Summary: > > > > [INFO] > > > > [INFO] Production ............................. SUCCESS [13.131s] > > > > [INFO] Hibernate Service ...................... SKIPPED > > > > [INFO] Production Commons ..................... SKIPPED > > > > [INFO] Host Adapter ........................... SKIPPED > > > > [INFO] Web Service Host .................. SKIPPED > > > > [INFO] Web Service Client ................ SKIPPED > > > > [INFO] File Host Adapter Service .............. SKIPPED > > > > [INFO] HostAdapterService ............................ SKIPPED > > > > [INFO] Socket Host Adapter Service ............ SKIPPED > > > > [INFO] Engineering Client Service ........................ SKIPPED > > > > [INFO] Standard Service ....................... SKIPPED > > > > [INFO] High Availability Service .............. SKIPPED > > > > [INFO] Production Web Application ............. SKIPPED > > > > [INFO] Step One ............................... SKIPPED > > > > [INFO] Production Utilities ................... SKIPPED > > > > [INFO] Production License Creator ............. SKIPPED > > > > [INFO] Configuration Service .................. SKIPPED > > > > [INFO] > > -------------------------------------------------------------------- > > -- > > -- > > > > [INFO] BUILD SUCCESS > > > > [INFO] > > -------------------------------------------------------------------- > > -- > > -- > > > > [INFO] Total time: 13.917s > > > > [INFO] Finished at: Tue Jan 10 17:51:03 EST 2012 > > > > [INFO] Final Memory: 5M/15M > > > > Thanks, > > > > > > > > GB > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
