You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ivica Loncar (JIRA)" <ji...@codehaus.org> on 2013/09/25 11:46:52 UTC

[jira] (MDEP-271) Allow for an empty prefix on dependency:build-classpath

     [ https://jira.codehaus.org/browse/MDEP-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivica Loncar updated MDEP-271:
------------------------------

    Attachment: MDEP-271.diff

Takes into account prefix and file separator properties.

Additionally, introduce useAbsolutePaths property. 

IMPORTANT: Introduction of new property will NOT break existing projects that rely on previous beahaviour (where outputAbsoluteArtifactFilename was set to false, but full path was returned). Otherwise we could reuse existing property and break existing builds.

                
> Allow for an empty prefix on dependency:build-classpath
> -------------------------------------------------------
>
>                 Key: MDEP-271
>                 URL: https://jira.codehaus.org/browse/MDEP-271
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: build-classpath
>    Affects Versions: 2.1
>            Reporter: Andreas Sewe
>         Attachments: MDEP-271.diff
>
>
> At the moment it is impossible to configure an *empty* prefix (classpath should contain just the artifact filenames, no paths) with {{dependency:build-classpath}}. Using an empty {{<prefix/>}} is the same as a non-existent {{<prefix>}}; all paths within the classpath are w.r.t. to the local repository (the default configuration). Setting {{mdep.prefix}} to an empty string as a workaround doesn't work either; you still get a leading slash for a path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira