]
Fred Bricon commented on JBIDE-9921:
------------------------------------
Tested a quick POC to see how we can plug ourselves to the dependency resolution error
markers.
Turns out we'll have to manually parse the error message to retrieve the missing
dependency information. Yuck!
Long term solution will require changes upstream :
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL:
https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: