[
https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-14003:
---------------------------------------
You can test this feature using the attached test13848a.zip project.
The project contains a hardcoded source attachment in .classpath as follows:
{code}
<classpathentry kind="lib" path="lib/commons-lang-2.6.jar"
sourcepath="C:/Users/Snjeza/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6-sources.jar"/>
{code}
Try the following:
- apply
https://github.com/jbosstools/jbosstools-central/pull/97
- import the project
- assert the source attachment is invalid
- assert the "Automatically configure the Java Source Attachment" preference is
checked
- open some class from the commons-lang-2.6.jar
The Source Lookup will download (if necessary) the source jar, attach it and open the
required source file.
You can see that .classpath contains a valid source attachment.
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
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