[
https://issues.jboss.org/browse/JBIDE-16743?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-16743:
-------------------------------------
I believe this is caused by
https://github.com/jbosstools/jbosstools-central/commit/dcd07cb8ca0b716fd...
(see JBIDE-14990, fixed in 4.1.0)
Basically, if it's a Maven project, we ignore source lookup to let m2e do its thing,
so as to not have 2 competing source lookup mechanisms for the same file.
On top of my head, I'd say we need a more fine-grained solution, where we check if
it's a jar from the Maven Library. I haven't debugged the problem, so I'm
probably missing something.
Sourcelookup does't work
------------------------
Key: JBIDE-16743
URL:
https://issues.jboss.org/browse/JBIDE-16743
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.1.2.CR1
Reporter: Rastislav Wagner
Assignee: Snjezana Peco
Priority: Critical
Fix For: 4.2.0.Beta1
Im trying source lookup on maven project according to
http://screencast.com/t/i6k9hzkjViOs but when I open class file, nothing happens.
Sourcelookup works for non-maven project with mavenized libraries.
--
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