This dosen't work for multiprojects release. I get a MultipleArtifactsNotFoundException.
site:site needs to have all the dependencies version of the project compiled and installed in the local repo to work. After release:perform, the pom are changed to the next version, but note rebuild. I would say the correct sequence is: release:prepare release:perform install site:site site-deploy Painfull. -tony dan tran wrote: > > Not possible yet! One work around is to write a shell to call site:site > site:deploy after release:perform using the same source tree. > > -D > > > On 4/19/06, Fredy <[EMAIL PROTECTED]> wrote: >> >> Hey all, >> is it possible to configure the release plugin that it is calling the >> goal >> site and site:deploy with the correct pom version? >> >> Thanks Fredy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/-m2--release-Plugin%3A-How-to-generate-deploy-the-site-while-releasing--tf1478573s177.html#a10176379 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
