[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-15392 at 9/10/13 7:02 AM: ---------------------------------------------------------------- {quote} Wouldn't it be the simplest to be able to create a class that provides all these default settings for the server type based on result from the beanloaders ? {quote} The API Rob created within this PR (RuntimeJarUtility) works this way. The only thing he would need to add is using a default configuration for JBoss AS < 7.0. {quote} And seriously - why can't sourcelookup just know about the runtime and if it does not know about it simply just return all jars ? then all this custom knowledge in sourcelookup goes away ? {quote} A source lookup container knows only a home directory because it can be used for non JBoss servers as well as for servers that aren't defined in Eclipse. This API should provide all jars from JBoss servers (excluding application's jars) based on a home directory. was (Author: snjeza): {quote} Wouldn't it be the simplest to be able to create a class that provides all these default settings for the server type based on result from the beanloaders ? {quote} The API Rob created within this PR (RuntimeJarUtility) works this way. The only thing he would need to add is using a default configuration for JBoss AS < 7.0. {quote} And seriously - why can't sourcelookup just know about the runtime and if it does not know about it simply just return all jars ? then all this custom knowledge in sourcelookup goes away ? {quoute} A source lookup container knows only a home directory because it can be used for non JBoss servers as well as for servers that aren't defined in Eclipse. This API should provide all jars from JBoss servers (excluding application's jars) based on a home directory. -- 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