I am thinking about an archetype, but I wanted to play around a little more with using this as sort of generating IDE bindings to the existing integration tests...perhaps an archetype would be better, I don't know.
IMO, an archetype means moving primarily to junit-triggered integration tests, which still leaves a requirement for the surefire plugin to mask out the integration tests on the unit-testing pass, then mask out the unit tests on the integration-testing pass...which is pretty awkward. I think if we added a general-purpose test-compile mojo to the compiler plugin - where the test source directory was configurable - then made sure the surefire plugin could handle test-class directory configuration, we could make this a little more elegant. For me, it's still simpler to run the tests I have in the assembly plugin and understand where they fail than it is to run the tests in the eclipse plugin and have any inkling into why they're failing...plus, the POM configuration is still simpler. -john On 12/6/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 6 Dec 06, at 1:05 AM 6 Dec 06, [EMAIL PROTECTED] wrote: > Author: jdcasey > Date: Tue Dec 5 22:05:43 2006 > New Revision: 482918 > > URL: http://svn.apache.org/viewvc?view=rev&rev=482918 > Log: > Working on a generator for junit wrappers for integration-test builds. > > Added: > maven/sandbox/plugins/maven-plug-it-plugin/src/main/java/org/ > apache/maven/plugin/plugit/GenerateJUnitWrapperMojo.java (with > props) Generating code, have you thought about using an Archtype? Jason. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
