nent" is
disabled and needs to be manually performed (e.g. using
setVariableValueToObject() or similar).
Benjamin Bentmann
--
View this message in context:
http://www.nabble.com/Execution-of-a-AbstractMojoTestCase-test-from-within-Eclipse-tf4034442s177.html#a13536244
Sent from the Maven D
er 27, 2007 12:12 PM
To: dev@maven.apache.org
Subject: Re: Execution of a AbstractMojoTestCase test from within
Eclipse
Benjamin Bentmann wrote:
>
> I would really appreciate some tweaks to the testing harness that
allows
> debugging using IDEs out-of-the-box.
>
Well, it seems I
ioned class path hacks.
Benjamin Bentmann
--
View this message in context:
http://www.nabble.com/Execution-of-a-AbstractMojoTestCase-test-from-within-Eclipse-tf4034442s177.html#a13444708
Sent from the Maven Developers mailing list
rer and used to register the Mojos with the Plexus
container.
That's all kind of hacking. I would really appreciate some tweaks to the
testing harness that allows debugging using IDEs out-of-the-box.
Benjamin Bentmann
--
View this message in context:
http://www.nabble.com/Execution-of-a-Abst
Sorry if I'm posting to the wrong list here.
I've been working on this for several days now with no solution coming
out.
The test works from within a Maven context, but when run it as a
stand-alone test from within Eclipse the following stack trace is
produced.
The Plexus look-up method
