[
https://jira.codehaus.org/browse/MNG-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279221#comment-279221
]
Jason Pyeron commented on MNG-5167:
-----------------------------------
- What problem you're trying to solve
Presently the local repository can only be specified as an absolute path or
relative to the current working directory (CWD). In a CMMI
(http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration) Level 3
and greater environment it is often a requirement to have all project
dependencies at all times (or at a minimum at release milestones) in the SCM
system.
Each developer workstation may not be configured identically and it would be
burdensome to expect a configuration change for a build tool.
By allowing project relative repository paths, the configuration can be
predicted and controlled.
- Why you think it's important
As a measure of importance, this patch is being used in production in 3
different companies in a production capacity presently. This patch allows a
switch to maven from a manual dependency management approach without breaking
policies.
- Examples of how it would be used
Project structure:
./
./bin
./lib/mvn
./src
./var/opt/apache-maven-3.0.4-SNAPSHOT/
./var/opt/apache-maven-3.0.4-SNAPSHOT/conf/settings.xml:
<settings><localRepositoryRelativeTo>M2_HOME</localRepositoryRelativeTo><localRepository>../../../lib/mvn</localRepository></settings>
> relative local repository settings
> ----------------------------------
>
> Key: MNG-5167
> URL: https://jira.codehaus.org/browse/MNG-5167
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Settings
> Affects Versions: 3.0.3, 3.0.4
> Reporter: Jason Pyeron
> Attachments: MNG-5167.patch
>
>
> see patch
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
