Hello, > What about we just change the lifecycle for the war plugin and add > phases there?
Because the same problem crops up time and time again which means the current solution is part of the problem. Imagine. I'm generating a database for my tests from XML descriptions. The intended control flow should be: - Copy resources (fill in DB connection details from some existing file) - Copy resources (convert model specific XML into "XML to SQL" tool specific XML) - Copy resources (turn the XML into SQL) - Copy resources (load DB with SQL) - Copy resources (classpath resources for tests) - Run the tests How can I make sure in my mojo that the many "copy resources" are executed in the right order? The idea of lifecycle is good but only as a big framework in which you can plug other things and you need a way to specify dependencies between the "other things", too. Regards, -- Aaron Digulla --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
