maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Showalter (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-4456) Deprecate fully qualified pathnames in system path
Date Wed, 18 Nov 2009 20:10:55 GMT
Deprecate fully qualified pathnames in system path
--------------------------------------------------

                 Key: MNG-4456
                 URL: http://jira.codehaus.org/browse/MNG-4456
             Project: Maven 2
          Issue Type: Improvement
         Environment: Any.
            Reporter: Jim Showalter
            Priority: Minor


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

        

Mime
View raw message