[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15392: ------------------------------------- Here's a summary of the use cases as Fred and I understand them. Please correct any information that seems wrong so that I can proceed with the patch: There are 3 use cases 1: source lookup / identification : when you enter a java class from the server in debug, we need to access that jar, so we can do some source attachement. Works for *any* jar used by the server 2: java search : in the IDE, user should be able to find any class from the server 'classpath'. IMO, that should be restricted to visible jars only 3: actually adding jars to the classpath of a dynamic web project or other project Items 2 and 3 should return identical jars, while item 1 should return a superset. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira