Thomas Fischer <[EMAIL PROTECTED]> writes: > Hi Arnaud, > > Thanks for you suggestion. Do you integrate the execution of the > integration test module in the build process of the plugin itself ? In my > current solution, if the code generated by the plugin cannot be compiled or > fails to do what it should, the plugin is not installed when "mvn deploy" > is called. I'd like to retain this if possible (I have come to appreciate > "no-brain approaches", they also work when time is short) >
No, I do not run IT as part of module build as this would entails a sort of chicken and egg problem ! There exists solutions such as plugin-testing plugin that can stage/unstage a plugin into repo so that IT can find them. But I'd rather take the simple course of using the maven-verifier API to remove the plugin from local repo if tests fails. I have never used this approach myself, the idea being that install works means UT works and IT works means deploy works so you'd run deploy iff IT passed. Take a look at the maven-verifier API, it is simple, straightforward and useful, without dependencies on anything else. Regards, BTW: this is what is used for IT maven itself. -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
