[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.webtools.jsf] Re: Programmatically add a existing component library to a JSF project

Off the top of my head, this looks like the "jar inside jar" problem that some Eclipse file location APIs have. What happens if you export the plugin in exploded form rather than jar form?

I should also note that in Galileo, the jsf libraries provider mechanism is deprecated. Going forward, JSF runtime and component libraries need to be provided through the new facet library provider mechanism.


Thanks,

Cameron

shilpa wrote:

Cameron,

I have implemented extension point org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries to add a few libraries when a new project is created using my library name.
It works fine when I launch an eclipse using my Plugin.xml for testing. but when I actually install the plugin, it throws an error and the jars doesn't get added. I feel the problem is in the way I am exporting or installing the plugin.

The error message is - Failed while installing JavaServer Faces 1.1.
assertion failed: Path for IClasspathEntry must be absolute: file:C:/Program


Files/IBM/SDPShared/plugins/plugins/com.hsbc.glti.jsf.taglibmetadata.jhx_1.0.0.jar!/lib/commons-beanutils-1.7.0.jar


Can you suggest some documentation which provides a clear picture of exporting and packaging the plugin? or if u know any solution to this problem