[
https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276586#comment-16276586
]
Andreas Sewe commented on MSHARED-604:
--------------------------------------
FYI, I also came across this issue today.
My use case: Resolve an artifact to some analysis and delete it afterwards. If
it its downloaded to the default local repository ({{~/.m2/repository}}) it
cannot be safely deleted, as others may use it. Hence, I want my own, temporary
local repository.
> 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-artifact-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.4.14#64029)
