So if I have a multi-module reactor... There's a jar module, a war module and a module for integration tests on the war module.
When I type `mvn4 test` should the reactor be smarter? It sees the need to run up to the test phase on all modules, and it sees that the integration tests module has a dependency on the war artifact... Then the packaging4 of war artifacts says the war dependency is produced by the `package` phase, so the build plan is upped to package for the war module The war module has a dependency on the jar module when packaging (the test phase can work with the classes directory in the war module) so the jar module is bumped to package as well Net result is that `mvn4 test` will work without having to populate the remote repo or local cache. Thoughts? I know it makes things more complex and involves enhancing the packaging descriptors... But I think this is what people expect -- Sent from my phone
