There's no "long" test. The idea here is to allow the developer to writer a simple project and invoke a goal within a unit test.
Indeed, there's probably a plugin version issue here, sorry about that (the EAR plugin for instance uses a forced settings.xml that will download the good version before starting the test; not perfect though). I'd be glad to finally find an acceptable solution of this testing technique. Thanks, Stéphane On 3/26/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
On 3/26/07, Brett Porter <[EMAIL PROTECTED]> wrote: > So, this indicates the problem with the test (and how to reproduce > it) - it can't depend on running the plugin itself unless it's an > integration test. The unit tests should be simplified to some > quicker, unit-testing tests, and the long tests made into integration > tests. I might help by rewriting the tests using the plugin-testing-harness. (That would fit "quicker, unit-testing tests", doesn't it?) Can you specify what the "long tests" are? I have no idea what to do in that area. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
