[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13851: --------------------------------------- {quote} How is this issue different from JBIDE-11970 ? Is it always the case that what is in source lookup makes sense to add to java search ? {quote} I haven't seen JBIDE-11970. This jira fixes a similar issue. The difference is that this feature includes all the classes from the Source Lookup plugin, not only those included in a runtime. {quote} This corresponds to a feature that was removed from m2e 1.0 : http://www.sonatype.com/people/2010/03/adding-dependencies-using-m2eclipse/ {quote} This jira isn't related to any m2e feature or to Maven in general. The jira solves the issue with the classes included in some WTP runtime, but aren't included in any Java Project. M2e has had a feature that finds a jar (GAV) based of a class name. It isn't related to Eclipse Java Search. I suppose it has been removed for the performance reason. Also, the same class can appear in a lot of different projects/packages (the Util class, for instance) so removing such a feature is logical. -- 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