On 11/23/05, Paul Spencer <[EMAIL PROTECTED]> wrote: > Brett, > 1) The current behavior allows abstract test classes to be compiled but > NOT executed, which is good. I currently use this functionality > on other projects.
ok, so that's a reason to keep it as is with both configurations. > > 2) The exclude list form the compiler plugin is not honored by the > surefire plugin relative compilation of the test source. In my > case the exclude list of the compiler plugin was the same as the > exclude list for the surefire plugin. All things considered, I am > not sure if the surefire plugin should inherit the compiler's exclude > list. the surefire plugin doesn't inspect it at all. the only way it is inherited is that if the test case is not compiled, surefire won't find it to run so it is implicitly excluded. > > 3) Is their a different compiler plugin used by surefire? > If yes, this what how is it addressed, i.e. artifactId? > I have verified that the compiler configuration tags, like <source> > and <target> in the surefire plugin configuration are not passed > to the compiler plugin. To me, this is a very minor issue. I > just mentioned it to pass along what I have learned. same artifact ID - to affect compilation the configuration must be on maven-compiler-plugin. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
