Simple table-based editor support is implemented.
There is no support for integration with the build path, or for configuration of dependency details (eg Dependency-URL, SHA1, etc).
There is simple support for LIBlet and JSR dependencies
The LIBlet project is a project in the current workspace.
Ideal workflow is that there is a way of choosing a project from the current workspace, and the other details (Name, Vendor etc) are completed automatically. In addition, the project dependency is added to the build path.
The LIBlet is sourced externally, and is located somewhere locally on the filesystem of the development machine.
Ideal workflow is that there is a way of choosing a LIBlet JAR file, and the other details (Name, Vendor etc) are completed automatically. The External JAR dependency is added to the build path.
Question: do we need to provide support for choosing a LIBlet by browsing to a JAD file?
Might the system then download the JAR if it isn’t local?
Current editor is a simple table editor.
However, this does not support the ideal workflow as described above.
Possible improvement is to change the editor to be more like the plugin.xml “Extensions” editor page, with two panels:
a list of dependencies;
the details for each, when selected.
We also need to decide how best to support JSR dependencies.