We have found this project to be extremely helpful, but are now having problems
moving a plugin-project to a new machine. While trying to figure out why our
project doesn't work (it is having problems with it-build-target) we found that
one of the unit tests fails consistently. The failure is
We want to add a link to the scm/connection to the dependency report for each
dependency we can get this information on. I think I have a good handle on
this but any hints would be appreciated, especially if somebody can suggest a
way to replace one of the configurable classes rather than wri
I am using the maven-plugin-testing-harness for general unit-testing of my
plugins, but I find that I need something to test how I am processing
dependencies. Does anybody have a good strategy for unit-testing behavior that
depends on the dependencies?
Thanks
Liz
[EMAIL PROTECTED]
