[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon edited comment on JBIDE-9921 at 11/26/11 8:22 AM:
--------------------------------------------------------------
As I already said, implementing quick fixes for JDT error markers doesn't make sense
in my opinion, as it could very well be caused by dependencies not being declared in the
pom.xml.
Regarding automatic download of the missing repos via the runtime detection mechanism, we
need to be able to access these repos via a public url.
Will open an enhancement request when that is available.
was (Author: fbricon):
Implementing quick fixes for JDT error markers doesn't make sense in my opinion,
as it could very well be caused by dependencies not being declared in the pom.xml
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL:
https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
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