[
https://issues.jboss.org/browse/JBIDE-16743?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-16743:
-------------------------------------
contributing features to m2e is not easy, believe me, even more so when stuff is not very
well self contained.
What we can do is :
* if it's a maven project with empty attachement, schedule the identificationJob with
a 1 sec delay. That should leave time for m2e to kick in and finish before we take over.
When the job is running, re-check if the source is still missing/invalid before actually
performing the lookup. This is clearly not ideal, but I believe should be enough 90% of
the time
* Maven project or not, If invalid source attachments are found (just move that
[
check|https://github.com/jbosstools/jbosstools-central/blob/master/maven/...]
up), kick the job immediately.
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