[
https://issues.jboss.org/browse/JBIDE-9688?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9688:
------------------------------------
Max, as I understand the problem, we would just force m2e to index the JBoss repo,
allowing its jars to be available during dependency searches/autocompletion. If the
artifacts found in the index are added to the pom without defining the repo explicitely in
settings.xml/pom.xml then dependency resolution would still fail, same as for a command
line build.
Just my gut feeling here. Needs to be investigated.
Add JBoss public repository to list of default repositories in
Eclipse
----------------------------------------------------------------------
Key: JBIDE-9688
URL:
https://issues.jboss.org/browse/JBIDE-9688
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: maven
Reporter: Rob Cernich
Assignee: Fred Bricon
Priority: Minor
M2e exposes an extension point, which allows plugins to contribute repositories to be
indexed. Automatically registering the JBoss repository seems like a sensible thing for
JBoss Tools. This would allow the user to access the JBoss public repository from the
tooling (e.g. add dependency) without requiring them to add the JBoss public repository to
their settings.xml file. Of course, the user would still need to ensure that the
repository was correctly configured within their pom so the project will build correctly.
The following is all that is required (in plugin.xml):
<extension
point="org.eclipse.m2e.core.indexes">
<index
indexId="JBOSS_NEXUS"
isShort="true"
repositoryUrl="http://repository.jboss.org/nexus/content/groups/publ...
</index>
</extension>
--
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