> What is the difference between... > > mvn war:exploded & mvn compile war:exploded ?
Note this in the WAR plugin docs: "Note: When using the war: goals it is assumed that the compile phase is already done. The WAR Plugin is not responsible for compiling the java sources or copying the resources." So "mvn war:exploded" won't run compile before attempting to run war:exploded. If you compiled recently or if you only changed code that does not need to be compiled (but merely copied to /target), this may be what you want. So go run "mvn clean war:exploded" as a test and see what happens, I doubt you will be happy with the results. > and the difference between... > > mvn compile war:exploded & mvn compile war:war ? Well, in this case, you are either going to get the result of war:exploded (the contents of a war file as a directory under target, not in war format) as output or the result of war:war (a war file) as output (essentially war:exploded PLUS the war packaging step). Either way Maven will compile the code in your WAR project prior to running either of the war plugin goals. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
