[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9921:
------------------------------------
I don't think hooking into JDT compilation errors is a good idea. If there is a
compilation problem, that means there's a missing dependency : that's where I
would try to add the quick fix (markers on the pom/project level)
If we consider there's a high probability we can achieve hooking up to the Dependency
Error markers, I can imagine adding the
jboss.org repos to the settings.xml but we'd
need to know where the EAP repo is coming from (user install / remote repo?) before adding
the relevant snippet. Maybe add a dialog box before changing the settings?
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira