See http://jira.codehaus.org/browse/MECLIPSE-192
maven-plugin-testing-tools builds the test jar by mangling the pom info to include the test version and then run BuiltTool.executeMaven() with the "package" phase to create the test jar. The side effect of this is to put test artifacts into D:\ide\workspace\maven\maven-eclipse-plugin\target\classes which is not good. I can see no work around for this situation except to use a different mechanism for testing. I noticed that there has been discussion about cleaning up the various invokers/unit testing frameworks that are sprouting up. The particular failures for the eclipse plugin are probably because they should be integration tests and not unit tests. Anyone have suggestions? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
