[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4889) JBoss Tools server runtime responds as capable of providing libraries for portlet facets although it doesn't provide them

[ https://jira.jboss.org/jira/browse/JBIDE-4889?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4889. -------------------------------- Resolution: Done By looking at some API I understand the issue more clearly. Apparently the first classpath provider to return a non-empty list of entries will be the only provider allowed to provide entries for that facet. This means that my provider claiming to provide entries is blocking other attempts to do it. However simply stopping returning entries in all cases leaves the ESB project, for example, with only references to their own ESB classpath container but not to the generic server entries which they may want. The fix for this is to make the ESB wizard add the server classpath container manually. I put a lot of thought to see if it truly belonged there, but it does. It wouldn't belong in the esb facet installation delegate, because adding the esb facet to a utility project should only really add the esb jars, not all the server jars. So the new ESB wizard is where the code to add all teh old entries belongs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira