[
http://jira.codehaus.org/browse/MNG-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231833#action_231833
]
Paul Benedict commented on MNG-1867:
------------------------------------
When it comes to system scope, the idea of hard-coding a file path into your
POM seems really counter-intuitive to the flexible nature of Maven. In my
opinion, such information is actually a user setting. Why not move that kind of
basic resolution into settings.xml? For example:
{code}
<system-dependencies>
<groupId/>
<artifactId/>
<version/>
<systemPath/>
</system-dependencies>
{code}
> deprecate system scope, analyse other use cases
> -----------------------------------------------
>
> Key: MNG-1867
> URL: http://jira.codehaus.org/browse/MNG-1867
> Project: Maven 2 & 3
> Issue Type: Task
> Components: Artifacts and Repositories, Design, Patterns & Best
> Practices
> Reporter: Brett Porter
> Priority: Trivial
> Fix For: 3.1
>
>
> possibly can avoid all use cases for system scope through proper use of
> alternate resolvers. Gather use cases (see MNG-1471) to ensure.
--
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
