[
https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-14663:
---------------------------------------
{quote}
but I've never seen any bug report about mismatch sources in m2e. If that was really a
problem, source validation could also be implemented directly in m2e.
{quote}
Open some source file using m2e, close it, remove its source jar from a maven local
repository and try to open the file again.
{quote}
However, the screencast clearly shows maven does its thing in the background, while we ask
the user if we should proceed. We have two source lookup mechanisms running concurrently.
This is wrong IMO, hence the reason why I wanted to treat maven differently.
{quote}
{quote}
Ok I managed to reproduce the behavior you showed. This is clearly inconsistent IMO.
{quote}
We have to remove the popup dialog.
Source lookup dialog shown twice on maven projects
--------------------------------------------------
Key: JBIDE-14663
URL:
https://issues.jboss.org/browse/JBIDE-14663
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Affects Versions: 4.1.0.Beta1
Reporter: Fred Bricon
Assignee: Fred Bricon
Labels: respin-b
Fix For: 4.1.0.Beta1
Source lookup dialog is shown twice on maven projects :
http://screencast.com/t/3yESat96FIw
I think our source lookup should ignore projects with the maven nature, since a m2e's
source lookup mechanism is already running in the background.
If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our
own stuff
--
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