I mean site-deploy not site:deploy :-) 2011/10/3 Miguel Almeida <[email protected]>: > On 3 October 2011 13:25, Olivier Lamy <[email protected]> wrote: >> using only: site-deploy rather than two goals: site:site site:deploy >> doesn't save you ? > > Olivier: yes, it would save me, if it was possible. But site:deploy requires > site:site. Running only site:deploy: > > Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy (default-cli) > on project parentA: The site does not exist, please run site:site first > > On Mon, Oct 3, 2011 at 1:28 PM, Stephen Connolly > <[email protected]> wrote: >> >> won't because he's using that crappy parallel mode if I read him right... >> > Actually, Stephen, the problem is not with Jenkins. Running the goal in CLI > yields the same result. > > I've set up a dummy project that exemplifies the issue. To run: > 1) In the pom.xml of the Parent, change the site's > <url>scp://localhost/home/user/mysite/</url> to a valid path > > Run "mvn clean site:site site:deploy" > > You will see that the plugin will ask you for the scp credentials (which are > part of the site:deploy goal) before running site:site in the modules. The > end result is that the timestamp (and contents) of your > home/malmeida/mysite/cobertura/index.html file will differ from > target/site/cobertura/index.html. Main difference in content: the deployed > one will be empty (because it was deployed prior to site:site on module1 and > module2); the one in target, after all maven goals complete, will be > complete. > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
-- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
