[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14663: ------------------------------------- Jars out of the maven classpath library are irrelevant. Whoever does that is shooting himself in the foot. We don't have to support that scenario. You already proved source attachments couldn't use variables, so be it. In the case of maven projects, it's not important since the hardcoded path is stored at the workspace level, not in .classpath that is shared among developers. Since we have not other way to provide source attachments, we warn the users about hardcoded paths. I think it's acceptable. The double dialog issue was not caused/related to maven. However, the screencast clearly shows maven does its thing in the background, while we ask the user if we should proceed. We have *two* source lookup mechanisms running concurrently. This is wrong IMO, hence the reason why I wanted to treat maven differently. I understand the advantages of your source lookup mechanism over m2e's, really, but I've never seen any bug report about mismatch sources in m2e. If that was really a problem, source validation could also be implemented directly in m2e. So I'm -0 about the "Enable Source Lookup for maven projects". -- 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