You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Thomas (JIRA)" <ji...@codehaus.org> on 2009/10/13 16:45:27 UTC

[jira] Updated: (MANT-61) Classpath generation should honour system-scope.

     [ http://jira.codehaus.org/browse/MANT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Thomas updated MANT-61:
-------------------------------

    Attachment: MNT-61.patch

I've added a patch against the 2.2-release.

What does it do:
* for system scope artifacts, the corresponding dependency is looked up and the systemPath is returned as path
* as the systemPath contains no more properties, each property value is replaced by its key, e.g. {{C:\project\target\archiv.jar}} becomes {{${${basedir}\target\archiv.jar}}}
* for system scope artifacts, no {{get-deps}}-entry is created

This allows for the generation of Ant files to be used in environments, where no Maven repository is available.

> Classpath generation should honour system-scope.
> ------------------------------------------------
>
>                 Key: MANT-61
>                 URL: http://jira.codehaus.org/browse/MANT-61
>             Project: Maven 2.x Ant Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Michael Thomas
>         Attachments: MNT-61.patch
>
>
> At the moment, dependencies are downloaded in the {{get-deps}}-target. For system dependencies, this is not necessary - the classpath-entries should directly reference the {{systemPath}}.

-- 
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