Mary,
As a potential topic for the meeting, can I suggest "Redistribution of
non-Eclipse libraries"?
There will be a growing number of
Higgins components which have dependencies on non-Eclipse libraries. For
example, the STS depends on 8 other jar files, and the LDAP CP depends on up
to a dozen.
An
easy thing for us to do is simply document which jars are needed and tell the
Higgins consumer to go find them all and put them it their classpath. That
solution seems somewhat unreasonable when viewed from the perspective of the
Higgins consumer. Other solutions could include:
* JPackage
*
Restricting Higgins components to only using jars that are available
as Eclipse components (even with this solution, I don't think there's an
Eclipse Package Manager, is there?)
*
Provide an "installer" which fetches the jars from the Internet as each
component is deployed (may be a nightmare in terms of broken
links).
*
Figure out how to deal with the licensing issues and just re-distribute the
jars (yay!)
Estimated time: 30 to 60
min.
Jim
