[ http://jira.codehaus.org/browse/MNG-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256726#action_256726 ]
Karl Heinz Marbaise commented on MNG-1867: ------------------------------------------ Currently i have the following example of using the system scope: {code} <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-common</artifactId> <version>${hadoop.version}</version> <scope>system</scope> <systemPath>${basedir}/hadoop-${hadoop.version}/hadoop-common-${hadoop.version}.jar</systemPath> </dependency> ... {code} This makes it possible to handle the situation where artifacts are not availabe as Maven artifacts (central..). I would suggest to make at least a scope available to have dependencies which are located within the current project. {code} <dependency> <...> <scope>project</scope> <systemPath>../...jar</systemPath> </dependency> {code} Furthermore the usage of things like tools.jar of the JDK would be usefull as well as mentioned earlier. > 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