You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/11/20 20:09:55 UTC
[jira] Closed: (MNG-4456) Deprecate fully qualified pathnames in
system path
[ http://jira.codehaus.org/browse/MNG-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4456.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-5
Assignee: Benjamin Bentmann
Added warning in [r882677|http://svn.apache.org/viewvc?view=revision&revision=882677].
> Deprecate fully qualified pathnames in system path
> --------------------------------------------------
>
> Key: MNG-4456
> URL: http://jira.codehaus.org/browse/MNG-4456
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.2.1
> Environment: Any.
> Reporter: Jim Showalter
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 3.0-alpha-5
>
>
> You could output a deprecation warning whenever a fully qualified path is specified, but not warn if the path starts with a variable.
> For example, this would generate no warning:
> <dependency>
> <groupId>com.sun</groupId>
> <artifactId>tools</artifactId>
> <version>1.6.0</version>
> <scope>system</scope>
> <systemPath>${java.home}/../lib/tools.jar</systemPath>
> </dependency>
> but this would:
> <dependency>
> <groupId>yuck</groupId>
> <artifactId>ugh</artifactId>
> <version>4.2.8</version>
> <scope>system</scope>
> <systemPath>C:/dumb/way/to/set/up/maven/dependency</systemPath>
> </dependency>
> That way at least users are warned when they're doing something dumb, and if they change to the variable-based form, they stand a fighting chance of having portable builds.
--
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