Hi Robert, Thanks for your quick answer, expecting the special cases handling !!!!! :-)
And now that you mention it, I remember wondering why it was not set to true by default :-). Sorry I might have missed reading some documentation, and that's my fault. thanks again tonio On Mon, Sep 30, 2013 at 6:30 PM, Robert Scholte <rfscho...@apache.org>wrote: > Hi Tonio, > > that's one of the reasons why I didn't changed this to the default > behavior for both plugins. > Current implementation checks if it is installing/deploying the final > module. If so, it will continue with the configuration of that module. This > should cover most of the usecases, so now we can gather those special cases > and start tweaking those plugins. > > Robert > > > Op Mon, 30 Sep 2013 23:11:12 +0200 schreef Tonio Caputo < > ton...@exeo.com.ar>: > > > Hi, >> >> I was trying this new great feature but, >> >> I found that if the last module of the project skips the install, it >> will not install any of the other modules. >> >> Is this the expected behaviour ? >> >> Just to let you know: >> >> My project last module is an integration-test that should be ran after all >> other modules are packaged, it should not be installed nor deployed, >> so it will be great if this configuration option can handle scenarios like >> this. >> >> >> Thanks in advance >> tonio >> PS: Seems maven-deploy-plugin version 2.8 deployAtEnd works in a similar >> way. >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<users-unsubscr...@maven.apache.org> > For additional commands, e-mail: users-h...@maven.apache.org > >
