[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...
]
Fred Bricon commented on JBIDE-14003:
-------------------------------------
{quote}Windows>Preferences>JBoss Tools>Source Lookup>Automatically configure
the Java Source Attachment
{quote}
My bad, I was looking at the wrong Eclipse instance Prefs page :-)
What Max proposed also contained "Warning: this will add a machine specific path to
your classpath settings."
As for the m2e container, ideally I'd have the m2e source lookup mechanism have
precedence over yours, but since it's not doable apparently and I can't see a
compelling reason now to prevent the SL plugin from fixing m2e's missing links, I can
live with that.
I'll do a more detailed code review tomorrow, but feature-wise, and provided you fix
the warning, that looks ok to me overall.
Automatically discover library sources for non-maven projects
-------------------------------------------------------------
Key: JBIDE-14003
URL: https://issues.jboss.org/browse/JBIDE-14003
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: maven
Affects Versions: 4.1.0.Alpha1
Reporter: Fred Bricon
Assignee: Snjezana Peco
Fix For: 4.1.0.Beta1
Attachments: test13848a.zip
As a follow up of JBIDE-13848, enable automatic discovery of library sources for
non-maven projects.
* This feature should be turned on/off in the preferences
* If the source file referenced in .classpath doesn't exist, it should attempt to
discover a new, valid one.
--
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