[
http://jira.codehaus.org/browse/MANTRUN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Kozelka closed MANTRUN-151.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.5
seems that version 1.5 uses {{settings.localRepository}} property for this
purpose
> provide a property always pointing to the currently effective local repository
> ------------------------------------------------------------------------------
>
> Key: MANTRUN-151
> URL: http://jira.codehaus.org/browse/MANTRUN-151
> Project: Maven 2.x Antrun Plugin
> Issue Type: New Feature
> Affects Versions: 1.3, 1.4
> Reporter: Petr Kozelka
> Fix For: 1.5
>
>
> Right now, there are at least 3 ways to define where local repository resides:
> 1) the default, ${user.home}/.m2/repository
> 2) settings.xml under /settings/localRepository
> 3) commandline property "maven.repo.local"
> Unfortunately, when writing ant fragments that need to access the local
> repository directly, there is no way to get effective local repo in all these
> cases.
> - I cannot use ant property "maven.repo.local" because it is only set if the
> corresponding maven prop.(3) is set
> - even adding fallback to default (1) still does not cover the case (2)
> I suggest introducing something like "settings.localRepository.file" which
> would always give me the right path
--
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
