Not at all ;-)
I'm talking about your own little Java class with a main (e.g.
com.ncs.AntInterceptor). Write it, compile it, add it a place on the
classpath where it can be found (in $ANT_HOME/lib something.jar for
example), and append com.ncs.AntInterceptor to ANT_OPTS.
When the ant.{bat|sh} script calls ant, it does:
java ... $ANT_OPTS org.apache.tools.ant.Main $ANT_ARGS
but unbeknownst to it, it will in fact call your com.ncs.AntInterceptor with
org.apache.tools.ant.Main $ANT_ARGS as argument. You do whatever you want
with the arguments, and turn around and call ant.
Is that clearer? --DD
-----Original Message-----
From: Shackelford, John-Mason [mailto:ShacJo@ncs.com]
Sent: Saturday, July 20, 2002 3:22 PM
To: 'Ant Users List'
Subject: RE: refactoring a large project
Dominique,
Ah, great idea! You are speaking of:
-inputhandler <class> the class which will handle input requests
right?
The properties file is in a well known location, but even if it weren't I
could use java.util.PropertyResourceBundle to load it from anywhere on the
classpath.
John-Mason Shackelford
Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
shacjo@ncs.com
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
|