[jbosstools-issues] [JBoss JIRA] (JBIDE-9921) Investigate if we can add quickfixes for missing dependencies/packages based on JDT and M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9921:
--------------------------------------------
about JDT compilation errors then that is actually easy to do - and other plugins do it
already, i.e. if you import org.junit.* but dont have it on the classpath the junit plugin
will suggest to add its classpath container (evil ;)
Similar Maven does or I think did do it previously to search Maven repositories for it -
but I believe they removed that.
But sure at pom level it becomes relevant and this is where we could ask the user to point
to a zip/directory and we set it up in maven settings.xml (optimally be able to download
it via the "downloadruntime" extension point snjezna made)
And yes - use the eclipse preview dialog before finishing the changes
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