ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roberto Juarez" <>
Subject RE: problems with <junit> task
Date Wed, 01 Sep 2004 15:44:37 GMT
I agree with you, though our team uses a different strategy. We have a CVS module of jars where
we control the libraries we use. We do not like to put junit.jar inside ANT_HOME/lib because
there could be the need for another copy of the junit.jar file in the lib directory of another
tool, ending with lots of junit.jars files spread over many locations. Instead we prefer to
download the jars module and have the scripts, launchers or whatever point to the right file
in the local copy of the jars module. Most of our computers have no CLASSPATH at all and every
script or launcher builds its own classpath. In the case we have been dealing with I have
a small shell script that sets the CLASSPATH to what is needed. When I fixed the line that
forgot to put junit.jar in the CLASSPATH everything was allright.



> -----Mensaje original-----
> De:	Erik Hatcher []
> Enviado el:	miƩrcoles, 01 de septiembre de 2004 17:14
> Para:	Ant Users List
> Asunto:	Re: problems with <junit> task
> On Sep 1, 2004, at 10:40 AM, Roberto Juarez wrote:
> > Thanks Erik,
> >
> > putting junit.jar in the system CLASSPATH correctly has made it work.
> Keep in mind that putting JAR's in CLASSPATH is not a recommended Ant 
> "best practice".  JUnit's JAR, from my perspective, is such an integral 
> part of my builds that I put it in ANT_HOME/lib and forget about it.   
> In fact, I commit Ant itself into our repository, so adding a 
> dependency like this for our whole team is really just a 'cvs commit' 
> for me.
> 	Erik
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message