Unless you have non-test code that depends on JUnit, you can probably remove this dependency altogether.
Maven was changed a while back so that the project didn't need the dependency, Maven automatically added it at test time. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers [EMAIL PROTECTED] wrote on 27/10/2002 09:35:29 AM: > sullis 2002/10/26 15:35:29 > > Modified: fileupload project.xml > Log: > updated JUnit version to 3.8.1 > > Revision Changes Path > 1.10 +1 -1 jakarta-commons/fileupload/project.xml > > Index: project.xml > =================================================================== > RCS file: /home/cvs/jakarta-commons/fileupload/project.xml,v > retrieving revision 1.9 > retrieving revision 1.10 > diff -u -r1.9 -r1.10 > --- project.xml 25 Oct 2002 04:52:27 -0000 1.9 > +++ project.xml 26 Oct 2002 22:35:29 -0000 1.10 > @@ -83,7 +83,7 @@ > </dependency> > <dependency> > <id>junit</id> > - <version>3.7</version> > + <version>3.8.1</version> > </dependency> > <dependency> > <id>servletapi</id> > > > > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> > > ForwardSourceID:NT00087056 -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
