Hi Mark, Thanks for your reply. I have been mixing 2 things. That's at least clear to me, now :).
Still, I do believe that the user should have the flexibility to decide whether the 'package' goal is executed as part of the tomcat:deploy goal or not. If I understand correctly, now he does not have this choice. All my web projects consist of 2 or more modules, and are built like a 'multiproject' (probably a M1 term). My development process is to first execute 'mvn clean:clean install' on the parent module, then subdir into the web module and call 'mvn tomcat:deploy'. If I'm doing something suboptimal here please let me know, since I always forget the 'dir' part. Then, to see that tomcat:deploy repeats a few steps is not a major issue, but slightly irritating it is. Anyway, thanks for the plug-in, since it helps me at least to deploy WAR-files to TOMCAT with a different context root than the plain file name. Do you have any idea when it becomes officially available? Cheers, Franck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
