if I'm right that's how NMaven works, dlls are copied to the target dir
On Tue, Sep 2, 2008 at 6:16 PM, James Carpenter <[EMAIL PROTECTED]> wrote: > You could avoid having NUnit on your path if you programatically use the > artifact resolver to pull down NUnit for you and throw it in the target > directory somewhere. (Usually target/plugin-name/....) I have done this in > the distant past. > > If you dig around in the maven mailing lists you will find a description of > how to do this. > > --- On Tue, 9/2/08, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > From: Wendy Smoak <[EMAIL PROTECTED]> > Subject: Re: Fixing integration tests and running them against 0.14 > To: [email protected] > Date: Tuesday, September 2, 2008, 10:59 AM > > On Mon, Sep 1, 2008 at 10:52 PM, Brett Porter <[EMAIL PROTECTED]> wrote: >> On 18/08/2008, at 8:15 AM, Carlos Sanchez wrote: > >>> Also is the convention to require NUnit explicitly listed in the pom >>> to run the tests? seems so as the tests need to be annotated with >>> NUnit annotations >> >> That would make sense to me - same as junit, etc in Java? > > It seems to have an added complication here-- if the installed version > of NUnit (nunit-console) is different from the one in the pom, it can > cause the tests to not run correctly. > > Java doesn't require that JUnit be installed and on your PATH. > > -- > Wendy >
