Hi, I am considering how to implement a real integration test for a plugin. The test harness is good for some purposes, but sometimes it is insufficient. This applies, in particular, when testing the dependencies, which are introduced by the plugin.
Here's my idea: I create the following projects: foo-Parent foo => dependency of => foo-Test foo-Parent would refer foo and foo-Test as modules. However, only foo-Test would name foo-Parent as its parent, but foo wouldn't. (The idea is, that I wouldn't want force people to download yet another pom.) Would that be working? Recommendable? Bad? Whatever? Regards, Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]