Vincent Massol wrote: > Yes you're right this is required (compiling, resources, packaging, etc). > For packaging I can provide an example. Imagine you're using Cactus. There's > a need to "cactify" the runtime WAR/EAR by adding Cactus jars inside WAR/EAR > and modifying deployment descriptors to add redirectors. That cactification > step would fit nicely in this packaging phase. Note that it could also be > done in the pre-integration-test/pre-functional-test phase but a packaging > phase would be cleaner.
Yep, that's what I was thinking of. > Sounds cool provided it's easy to add a new surefire-xxx from outside. I > mean imagine I'm working on the Cactus project and I want to create a > surefire-cactus. Could I provide it as a jar in the Cactus repository and > could it then be wired somehow so that the surefire plugin would use it? Part of cactus (just like how the scm plugin works, for example). > > I'm still unsure of the need to have a single surefire plugin for tests with > different providers. The alternative would be different test plugins all > using a common surefire jar for the basic execution (delegation vs > inheritance). That would make it difficult to set up a default lifecycle, but its probably a case we need to deal with anyway so its possible to pass in the necessary configuration. We can work this through with the testNG contribution. > If we had this then the report mojos could be put in the different test > plugins. This means running tests requires downloading a bunch of (usually larger) site stuff that the average joe building the project might not want. Would rather keep them separate. > Hmm... I'm starting to wonder if defining the workflow in pom.xml wouldn't > be too complex after all and maybe it would be better defined in a cactus > plugin. I think its possible in the POM, but makes more sense in cactus so that the same solution is easily used whatever is being used to run them. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
