[
https://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-395.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: https://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
>
> In a corporate environment, we have the local repository not located in the
> standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties
> org.apache.maven.user-settings and org.apache.maven.global-settings (our
> settings are also not located in the standard locations
> ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse
> integration tests are using ${user.home}/.m2/repository, thus don't find
> dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and
> Settings/XXXX/.m2/repository)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
