Didn't understand a thing ;-) This is getting too advanced for me. --DD
-----Original Message-----
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 22, 2003 10:55 AM
To: Ant Developers List
Subject: ReferenceHelper - interceptor
I'm still here with my ReferenceHelper waiting for a generic enough to
show.
What about an interceptor that creates a classpath from the jars in a
dir lazily?
For example, usually we do something like:
<classpath id="project.classpath">
<fileset dir="lib">
<include name="**/*.jar"/>
<include name="**/*.zip"/>
</fileset>
<pathelement location="classes"/>
</classpath>
<javac srcdir="${src}"
destdir="${build}"
fork="true"
classpathref="project.classpath"
/>
But with a "jardir" interceptor, we could do:
<javac srcdir="${src}"
destdir="${build}"
fork="true"
classpathref="jardir:lib"
/>
Basically it gives a reference from a classpath created on-the-fly.
Now, is this something we want?
Without this interceptor, we could do:
<javac srcdir="${src}"
destdir="${build}"
fork="true"
classpathref="${jardir:lib}"
/>
The PropertyHelper would create the classpath, give it id="jardir:lib",
and then the reference system would use that to get it.
Basically we would have most of the functionality without having to make
specialized hooks.
If there are other compelling use-cases I'd be happy to see them.
In the meantime, MHO is that to KISS maybe not having reference
interceptors could be ok.
Opinions?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
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]>
