[
https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-14003:
-------------------------------------
So I tried it and got :
http://screencast.com/t/wNnLEZIk
* 'jarname' should show the original jar name
* I think the message should somehow emphasize a non-portable path will be used to store
the source attachment link.
* there are no workspace prefs that'd allow a user to turn that feature on/off
* 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)
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