[jbosstools-issues] [JBoss JIRA] (JBIDE-17241) Forge should use the m2e settings.xml during Maven artifact resolution

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985448#comment-12985448 ] 

Max Rydahl Andersen commented on JBIDE-17241:
---------------------------------------------

okey - how about when I use the console and run commands here ?

> Forge should use the m2e settings.xml during Maven artifact resolution
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-17241
>                 URL: https://issues.jboss.org/browse/JBIDE-17241
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: forge
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Vineet Reynolds
>            Assignee: George Gastaldi
>             Fix For: 4.2.0.Beta3
>
>
> When I have a project like TicketMonster or any of the WFK examples in my workspace, I configure m2e to use a separate settings.xml file (say ~/.m2/contributor-settings.xml or ~/.m2/redhat-repos.xml) which point to the RedHat enterprise repositories or other repos. My usual settings.xml file lacks this.
> Forge uses the ~/.m2/settings.xml file by default, even though the Eclipse workspace uses a different one. From the point of view of end-users this results in weird behavior in Forge. For example, Forge facets are not activated correctly because the Maven artifacts in the Red Hat enterprise repo could not be found.
> It requires the user to modify the content of ~/.m2/settings.xml instead of just pointing to a different one, which is a bit unreasonable of Forge, given the current capabilites of m2e.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)