This is weird. I mean, the POM contains all the information Maven needes to understand that e. g. a MVN test on the dependent module implies an (at least) MVN package on the dependency side. Otherwise the relationship provided in this multi-module project could not get fulfilled. So why is MVN not simply acting in a logical way and package the dependency even when the invocation just enforced a MVN test? That would do not harm and it would make everything work as one expects.
-- View this message in context: http://maven.40175.n5.nabble.com/multi-module-phases-sequence-tp5789365p5789681.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
