On 05/04/2011, at 1:16 AM, Jesse Glick wrote: > There seems to be no decent solution using current --also-make. The solutions > using the styles I proposed previously would look like: > > 1. mvn -am -pl submodule test-compile -then -pl submodule test > > 2. mvn --also-make-goals -pl submodule test-compile test > > 3. mvn --also-make-smart -pl submodule test [where test known to presuppose > test-compile in dependents; compile would suffice if there were no deps on > secondary test artifacts] > > (An IDE user might ask the IDE to just run JUnit on > submodule/src/test/java/**/*.java bypassing Maven and Surefire and using some > IDE-specific compilation of dependencies from sources, if the IDE has been > configured to run tests exactly the same way as the POM specifies Surefire > should run them, but it would be best if command-line Maven could do this to > begin with.) > > Does the issue make sense now, and is it worth filing a JIRA ticket for this?
It makes sense. Of the solutions, 2 seems clearest, though the test-compile should sit with the --also-make-goals parameter. However, I'm not sure how many people would use this - it's quite some entry complexity to gain a little more runtime efficiency. I've always thought the solution to these type of problems was to invest more effort in incremental builds (don't run tests if no code + dependencies changed). - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
