Reuse [was: build.classpath and tinderbox builds]

[Sam Ruby <ru...@us.ibm.com>]

Jeff Martin wrote:
>
> Think this is going to be one of the problems with XSL,
> poor reusability. Can't really reused code apart from
> cutting and pasting sections. I like the idea of the
> dependacies, it is something that has crossed my mind
> before but i could think of a way to do it (at least
> not a nice way)

Cutting is pasting is fine with me - if it makes sense to integrate
anything from my code, I certainly have no interest in continued
development on a parallel effort.

Besides, at the moment there may be more possibility for reuse than you
think - the way I chose to approach the problem was as a SERIES of XML
transformations in a pipeline.  Perhaps not the most efficient, but it made
the process much more understandable to me, and much easier to debug (I
could directly view the intermediate results).

Attached below is the code for sorting dependencies.  Note: the error
message for the recursion is not currently correct - if A depends on B, and
B depends on A, and C depends on A, then it may choose to output C; clearly
a victim not a villian.  I plan to get back and correct this eventually.

- Sam Ruby

(See attached file: sortdep.xsl)