[ https://issues.jboss.org/browse/JBIDE-13848?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13848: --------------------------------------- {quote} {quote} if a source attachment file doesn't exist, the Source Lookup will try to find a new file. {quote} I don't understand. You're describing the source lookup principle {quote} No. If there is a non-empty source attachment, the action won't be started even if the source jar doesn't exist in the file system. I will add the following feature: - check if the jar exists - start the action if it doesn't exist Your question: {quote} Is that JBIDE-13852? I thought it wasn't done yet? {quote} Answer: This feature isn't related to JBIDE-13852. {quote} Can you please open a new JIRA for that, so you can reference subsequent fixes? {quote} JBIDE-13852 is a separate jira that isn't fixed yet. {quote} I agree with the fact users will prefer having the source code than not, my point was more about having .classpath getting non-portable changes behind the user's back (m2e uses a classpath container so it's not the same thing). {quote} The source attachment action isn't related to a container. The action is called whenever the Java editor is activated. M2e requires a project to be a maven project and can't find an artifact if it doesn't exist in a m2e indexer. I will add a new property that will be true by default. {quote} M2_REPO will stay there as long as m2e-wtp needs it, don't worry (EARs can't use classpath containers) {quote} No matter of that, a user could remove his local maven repository and M2_REPO won't help. Checking for existence of the source jar will always help. -- 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