[mojo-dev] [jira] (MGWT-175) Warnings from tests that are excluded during gwt:test

[Thomas Broyer (JIRA)]

Thomas Broyer closed MGWT-175 as Won't Fix Warnings from tests that are excluded during gwt:test GWT scans all files on the "source path" (within the classpath), regardless of which tests to run. The only possible fix would be to settle on a project layout where GWTTestCase go into src/test/gwt rather than src/test/java and using a special invocation of the maven-compiler-plugin to compile them into a different directory than target/test-classes (e.g. target/gwt-test-classes) so that we could run gwt:test with that output directory in the classpath in place of target/test-classes. That would preclude sharing code between src/test/java and src/test/gwt, unless src/test/gwt (or target/gwt-test-classes) is also used with the maven-surefire-plugin. I don't think this is worth it, given these messages don't fail the build. It's far easier to "segregate" your tests in packages so that you don't mix JUnit4 and JUnit3 tests in the same package. Alternately you can explicitly exclude JUnit4 tests from the source path using an exclude patter in your gwt.xml. Change By: Thomas Broyer (14/Jun/12 8:08 AM) Resolution: Won't Fix Status: Open Closed

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email