[
https://issues.jboss.org/browse/JBIDE-16743?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-16743:
---------------------------------------
In my opinion, that would make this feature more complicated, especially if it will work
occasionally (90%).
It would be enough to do the following:
- call our source lookup for all Java projects
- remove the Source Lookup dialog (it already doesn't solve the issue with hardcoded
paths)
Advantages:
- it is simple
- it will always work if there is a source file in some repository
- we will avoid the issue with the dialog I have previously described
- a user could disable our source lookup in general if he doesn't want it for some
reason
{quote}
we ignore source lookup to let m2e do its thing, so as to not have 2 competing source
lookup mechanisms for the same file.
{quote}
Our source lookup and m2e lookup aren't two competing mechanisms. There are no any
issues if both of them find a source file (it will be the same file) except unnecessarily
showing the Source Lookup dialog.
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