All tasks defined at startup (that is the lib directory of ant, contain ant.jar and optional.jar), only work when all libraries called by these tasks are already known to ant (or are in the lib directory, which is added to the classpath). So if you taskdef the junit task under a different name, you probably don't have to have junit in your lib directory (eg taskdef name="mavenjunit").. Or maybe extending the junit task with a new name and then do a taskdef on that, if the simple taskdef shouldn't work..
BTW.. I don't want anyone to touch my ant_home/lib.. You can get some nasty surprises when there is too much in there or stuff in there that you don't know that it is in there.. Mvgr, Martin On Tue, 2002-06-04 at 17:51, Vincent Massol wrote: > Hi, > > Just a probably stupid question. Why do we need to ask Maven users to > have junit.jar in anthome/lib ? Couldn't we download it in the same way > as we download the other jars ? > > Thanks > -Vincent > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
