Test source dependencies not configured correctly in some cases

[tbroyer]

Test source dependencies not configured correctly in some cases

[tbroyer]

This is because the maven-source-plugin is bound to the prepare-package (or even package) phase, which comes after the test phase. As you need sources for GWT tests, then either run source:jar earlier, or always run at least up until the prepare-package or package phase.

This is purely a Maven "issue" from my PoV, due to its linear lifecycle and how it's applied to reactor builds. I personally consider the only 2 phases you should use as goals when calling a multi-module build are package and verify. (install and deploy have specific uses --namely share the built artifacts with other projects, or working around ill-designed plugins or Maven lifecycle-- so does clean, obviously)

[ibaca]

Thanks! Using the package goal is ok.

Just one thing. Looks like you admit that the test goal is broken at the test phase (maven problem), why don't you set the default phase of the TestMojo to PREPARE_PACKAGE (or PACKAGE) so is clear that the plugin requires at least this phase to work properly. Or one step further, use INTEGRATION_TEST which solve the problem and is still meaningful.

[tbroyer]

Because the test phase is when it's appropriate to run tests, and it works OK on one module. The problem arises in multi-module builds when you have dependencies on non-gwt modules where the maven-source-plugin is used. The proper fix (if you want it) is to run source:jar earlier, or just always use package at a minimum in multi-module builds.