[ https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14003: --------------------------------------------- That truly sucks if sourcepath can't use variables [1] - this also means we are forced to hardwire hardcoded paths into data that is potentially shared with others - which in the case of non-maven projects is very likely since there is no other way of sharing the basic setup. I would really like to be able to have this feature enabled by default, but we can't do that with its current workflow (it injects hardcoded paths into files that are most likely shared with a team). Could we show a dialog when the match is found and let the user be aware what happend/is about to happen ? Something like: Title: Found source jar for 'jarname' Text: 'jarname' is missing a valid source attachement. Found a a match at <name/path of where it is found (remote or local)>. Do you want to use this as source for 'jarname' ? Warning: this will add a machine specific path to your classpath settings. [ ] remember my decision for other jars [Always] [Yes] [No] No - nothing is done. Yes - add, but ask next time again Always - just do it. WDYT ? [1] http://stackoverflow.com/questions/9286074/using-variables-for-source-att... -- 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