On Friday 25 April 2003 11:54, Stefan Bodewig wrote:
> On Fri, 25 Apr 2003, peter reilly <[EMAIL PROTECTED]> wrote:
> > I do not see the problem here: suppose Path implements
> > dynamicElement(Path path)
> >
> > one could do:
> > <javac>
> > <classpath>
> > <PathThatIgnoresBuildSysclassPathToTrickGump>
> > <pathelement path="${classpath}"/>
> > </PathThatIgnoresBuildSysclassPathToTrickGump>
> > </classpath>
> > </javac>
>
> I don't want to use it as nested element of <classpath>, but as nested
> element of <javac>.
Why and how (from an xml point-of-view)?
javac takes five different path sub-elements - <src>, <classpath>,
<sourcepath>, <bootclasspath> and <extdirs>, the build xml author
would always need to specify which one is to be used. I suppose one
could do some thing like:
<javac>
<classpath.PathThatIgnoresBuildSysclassPathToTrickGump>
<pathelement path="${classpath}"/>
</classpath.PathThatIgnoresBuildSysclassPathToTrickGump>
</javac>
>
> Take <classfileset>/<zipfileset> and <dependset> as another example
> (where you can trick me ;-).
Ok :), use <outofdate> with <deletetargets/> (untested xml follows..)
<outofdate>
<sourcefiles>
<zipfileset/>
</sourcefiles>
<targetfiles>
<classfileset ...>
</targetfiles>
<deletetargets/>
</outofdate>
<
>
> I want to be able to be able to use <classfileset> as <srcfileset> and
> <zipfileset> as <targetfileset> - or the other way around.
This is the same problem as javac, how does the build author specify
if the fileset is a src fileset or a target fileset.
Cheers, Peter
