[jbosstools-issues] [JBoss JIRA] (JBIDE-14003) Automatically discover library sources for non-maven projects

[ https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14003: --------------------------------------- {quote} 'jarname' should show the original jar name {quote} Fixed. {quote} I think the message should somehow emphasize a non-portable path will be used to store the source attachment link. {quote} Max has proposed that message. {quote} there are no workspace prefs that'd allow a user to turn that feature on/off {quote} Windows>Preferences>JBoss Tools>Source Lookup>Automatically configure the Java Source Attachment "Prompt" is the default. {quote} I haven't tried / checked if the code works on classpath containers. If it does, then the Maven container should be ignored to prevent collisions (use hard coded links when m2e can do better) {quote} The code works for classpath containers. Re the Maven container, m2e also uses hardcoded paths. However, source attachments for the Maven container aren't saved in the workspace (.classpath), but in the m2e.jdt plugin instance area. The Source Lookup plugin works the same way. The Source Lookup plugin will additionally check whether a source attachment file exists and, if it doesn't exist, will try to download it again. M2e ignores invalid source attachments. If m2e has added a valid source attachment, the Source Lookup plugin won't do anything. -- 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