This is persuant to the patch I sent recently for the
TWO: KISS philosophy and orthogonality of tasks argues that rather than
adding lots of features to every
task, we code up smaller, simpler tasks that can be combined. Hence,
you have and ,
NOT a giant javac task with depend functionality included. Example:
Approach one requires adding a nested "dependencies" fileset to the
Approach two requires slightly enhancing the merge mapper to support a
list of target files.
Comments, opinions, questions, alternative approaches?
I am happy to submit a patch either way...
Craeg K. Strong | www.arielpartners.com
Ariel Partners LLC | email@example.com
85 River Street, Ste. 3A | Fax: (781) 647-9690
Waltham, MA 02453 | Voice: (781) 647-2425