[
http://jira.codehaus.org/browse/MNG-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138495#action_138495
]
Brett Porter commented on MNG-3588:
-----------------------------------
sorry, all I meant was has the setting you are trying to use worked in a
previous version of Maven in your experience?
If you do wish to write a test case that exhibits a problem, the instructions
are here:
http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test
> ${maven.repo.local} in settings.xml doesn't work.
> -------------------------------------------------
>
> Key: MNG-3588
> URL: http://jira.codehaus.org/browse/MNG-3588
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: Marcin Kuthan
> Priority: Minor
> Fix For: 2.0.x
>
>
> I can't use ${maven.repo.local} parameter inside settings.xml file. The
> parameter is simply ignored.
> <settings>
> <localRepository>c:\base_repo_location</localRepository>
> <profiles>
> <profile>
> <id>my-profile</id>
> <properties>
>
> <maven.repo.local>C:\alternative_repo_location</maven.repo.local>
> </properties>
> </profile>
> </profiles>
> </settings>
> When I run
> "mvn -P my-profile package"
> all downloaded artifacts are stored under "c:\base_repo_location" not
> "C:\alternative_repo_location".
> When I run
> "mvn -Dmaven.repo.local=C:\alternative_repo_location package" package
> artifacts are stored under "C:\alternative_repo_location" as I expected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
