[
https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780277#comment-15780277
]
Dan Tran edited comment on MSHARED-604 at 12/27/16 12:19 PM:
-------------------------------------------------------------
Thanks for the suggestion, however, it does not work either. Debug thru the
code, no traces of maven-artifact-transfer interacting with local repo set
under buildingRequest.
was (Author: dantran):
Thanks for the suggestion, however, it does not work either. Debug thru the
code, no traces of aether interacting with local repo set under
buildingRequest.
> 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)
