Tests defined in the eclipse plugin have to be completely refactored. With the shitty plugin why not. I already opened several issues to separate unit and integration tests and also to refactor the plugin itself. Actually, I don't want to begin all those changes if we didn't finish to apply/reject existing patchs in Jira. I'm working on MECLIPSE-344. If you want to help me to cleanup Jira ;-)
Arnaud On Dec 13, 2007 2:58 PM, nicolas de loof <[EMAIL PROTECTED]> wrote: > Hello > > I tried to look at maven-eclipse-plugin tests and was really confused on > it's testing framework complexity. > > What about moving thoses IT tests to src/it via the Shitty maven plugin ( > http://mojo.codehaus.org/shitty-maven-plugin/usage.html) > I allready used it and found it simple to use and very powerfull. > The only difficulty AFAIK is to refactor the generated file verification > to > be used from validate.groovy scripts. > > > I also got some errors running the tests as my local repo contains some > source jars, so the generated .classpath files does not match the expected > ones. > > Maybe those tests should rely on a test localrepository and a test > remoterepository to avoid such false-failures > > Nico. > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
