Library Provider Framework was first introduced in eclipse 3.5 to solve the messy library management in eclipse WTP in whole, which include JPA (Eclipse Link), JSF, etc.)

Basically it defines interface and abstract layer for manage JDT's classpathcontainer specially for web apps. And also it provides some concrete library providers. These include downloadable library provider, User Library Provider, OSGI library provider. Also the framework manages library provider lifecycle, which fits in eclipse faceted project lifecycle. This lifecycle includes creation, building model, passing model to GUI thread, execution for project building.

Previously we used downloadableLibraryProvider in OSS version. There are basically 2 problems. One is that some companies do allow zip file downloading so that they won't be able to use ICEFaces tool. 2nd is that it cannot be used for EE version.

For EE edition, we developed a libraryProvider which was used in 1.8.2.GA_P01. But it was based on eclipse 3.5 in which icefaces and facelet support were separated. That libraryProvider is not customizable so that 2 set of provider code based used in two plugins. But in eclipse 3.6 jsf and facelet support are merged in one. Thus I cannot to use it anymore.

For above reason I have to develop a new LibraryProvider called PluginSuppliedLibraryProvider framework. This provider plugin is packaged as a standalone package/feature. Icefaces plugin can declare any number of libraries packaged as each individual plugins.

This one is now used in both ee and oss eclipse plugins.