-
Feature Request
-
Resolution: Done
-
Critical
-
None
-
As Maven integration is new for JBDS 5, a release note of this feature is not required. All Maven functionality will be covered in the Overview section of the Release Notes and in the documentation.
-
Not Required
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.
