Maybe it would need that library writers follows a convention, putting an XML file somewhere in their site describing their library and how to get it. Like Eclipse Update system.
Otherwise, you would need to provide this information by hand for each (well known) library, which isn't very practical. But it would has the advantage to work with libraries that has currently little or no maintenance.
A mixed approach (first a manual list, then using update sites if available) would be the most practical, making the tool to work at first, but then progressively relying on discipline of library writers (would also require more uniform zip structure...*), allowing better/faster updates.
* Fast scan of some library archives I have: I see structures like:
<lib name>/library/<lib name>.jar (ideal)
libraries/<lib name>/library/<lib name>.jar
<lib name>-003/<lib name>/library/<lib name>.jar
<lib name>-20090602/library/<lib name>.jar (worst!)
library/<lib name>.jar (bad too...)
and so on... There are other directories at the "/library/" level, like examples, src, source, reference, documentation, docs, and various licence/readme files.
No wonder that newbies are lost, sometime...
For legacy, I suppose the best is to locate the "/library/" folder and manage from there. Must also find the proper .jar name, sometime there are several there... Some good heuristic will be needed...
