For historical reasons, DepAn originally loaded only a single jar.
But there is no reason not to load Bytecode information from a list of
sources. This might not follow exactly the semantics of classpath (i.e.
should type definition in the early part of the list dominate over latter
definitions of the same class?).
The UI that currently allows selecting jars or a directory should create a
list of Bytecode input sources. Buttons should provide Add Directory..,
Add Jar.. browsing services and a Remove button. (See
<Java Build Path>.Libraries tab for a related example.
Original issue reported on code.google.com by le...@google.com on 12 Sep 2008 at 5:26
Original issue reported on code.google.com by
le...@google.com
on 12 Sep 2008 at 5:26