Antoine Lévy-Lambert wrote:
I do not know whether it is 100% related,
but there is an open bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3198 concerning the <javac/> task
in the case where the same source file is present in several source paths.
Will we be better fit to solve this problem with the new mapper infrastructure ?
No I do not think so.
The issue with the javac task is I think the fact that it is a MatchingTask and cannot take
embebedd filesets as nested elements.
The person wants to do this:
javac -sourcepath src1;src2 src1/x/Test.java src2/x/AnotherClass.java
where src2/x/Test.java and src1/x/AnotherClass.java may exist, but the user does not want to compile them.
A javac task with embedded srcfileset may look like this:
<javac destdir="classes"> <!-- note: no source dir set -->
<srcfileset dir="src1"> <!-- note: this gets mapped to -sourcepath src1 -->
<include name="x/Test.java"/>
</srcfileset>
<srcfileset dir="src2" includes="x/AnotherClass.java"/>
</javac>Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
