maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MSHARED-604) Honor none default localRepository
Date Tue, 27 Dec 2016 11:57:58 GMT

    [ https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780255#comment-15780255
] 

Guillaume Boué commented on MSHARED-604:
----------------------------------------

To change the local repository, you can use the {{RepositoryManager}} class, and call {{setLocalRepositoryBasedir}}
by passing it the {{ProjectBuildingRequest}}:

{code:java}
@Component
private RepositoryManager repositoryManager;

buildingRequest = repositoryManager.setLocalRepositoryBasedir( buildingRequest, localRepositoryPath
);
{code}

I am not sure what the {{localRepository}} field is doing, perhaps it should be removed.

> Honor none default  localRepository
> -----------------------------------
>
>                 Key: MSHARED-604
>                 URL: https://issues.apache.org/jira/browse/MSHARED-604
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-aritfact-transfer
>    Affects Versions: maven-artifact-transfer-0.9.0
>            Reporter: Dan Tran
>
> ArtifactResolver ignores localRepository settings in the request ProjectBuildingRequest.
 It always use the default location when maven starts
> Use case:  I have a use case to resolve a maven artifact with local repo is under maven
'target' directory
> maven-compat does work my case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message