Currently, our build uses a modified distribution of Ant - all the
optional libraries we need are bundled into the lib directory. We use a
similarly modified version of Eclipse (i.e. the Ant part has the same
changes made).

Needless to say, this is somewhat suboptimal. I want to move to a system
where we can change versions of Ant and Eclipse easily, without having
to perform the modifications again. With imports, this isn't too hard
(because I can have our own "lib" directory with a taskdefs.xml project
which can be imported from any build which needs them). I believe this
should solve our problems for everything *except* for Junit.

None of the solutions in the FAQ seem very satisfactory to me,
unfortunately - they're not upgrade-friendly. Here are my ideas:

1) Copy the JUnit jar file into ant/lib if it's not there already, and
document the fact that tests won't work first time.
2) Remove ant-junit.jar from ant/lib if it's there, and document the
fact that tests won't work the first time.
3) Tell everyone to have an ANT_OPTS environment variable of "-lib xxx"

Again, none of these are terribly appealing, but at least they don't
require changing stock installations beyond what is possible within a
build file itself. Of course, they *do* require knowing where the
ant/lib directory is - is there a recommended way of knowing that?

Possibly modifying the stock Ant just to remove ant-junit.jar is the way
forward. (I prefer this to adding the junit jar file to ant/lib, as that
makes it harder to change versions of Junit.)

For Eclipse, I can modify our "template workspace" to give Ant an extra
global entry to the JUnit jar file. That shouldn't be too bad.
 
Jon Skeet
Senior Software Engineer
CLEARSWIFT
The MIMEsweeper Company

DDI:               +44 (0) 1189  038  109
Mobile:           +44 (0) 7970 158 865
Switchboard:   +44 (0) 1189  038  903 
Fax:               +44 (0) 1189  039  000      
Web: www.clearswift.com 


Clearswift monitors, controls and protects all its messaging traffic in 
compliance with its corporate email policy using Clearswift products.
Find out more about Clearswift, its solutions and services at 
http://www.clearswift.com

This communication is confidential and may contain privileged information 
intended solely for the named addressee(s). It may not be used or disclosed 
except for the purpose for which it has been sent. If you are not the intended 
recipient, you must not copy, distribute or take any action in reliance on it. 
Unless expressly stated, opinions in this message are those of the individual 
sender and not of Clearswift. If you have received this communication in error, 
please notify Clearswift by emailing [EMAIL PROTECTED] quoting the sender and 
delete the message and any attached documents. Clearswift accepts no liability 
or responsibility for any onward transmission or use of emails and attachments 
having left the Clearswift domain.

This footnote confirms that this email message has been swept by MIMEsweeper 
for Content Security threats, including computer viruses.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to