You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 13:51:00 UTC

[jira] [Updated] (MDEP-488) Build-classpath for maven repository layout

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

Elliotte Rusty Harold updated MDEP-488:
---------------------------------------
    Issue Type: Bug  (was: Improvement)

> Build-classpath for maven repository layout
> -------------------------------------------
>
>                 Key: MDEP-488
>                 URL: https://issues.apache.org/jira/browse/MDEP-488
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: build-classpath
>    Affects Versions: 2.10
>            Reporter: Gaƫl Lalire
>            Priority: Major
>         Attachments: classpathPatch.diff
>
>
> Build-classpath cannot create a classpath for a maven repository layout in multimodules projects.
> Indeed project.artifacts returns artifacts whose file may be from the local repository or from your project target directories.
> For last one the replace mechanism failed.
> We could execute the build-classpath with invoker plugin as a workaround but it is not clean.
> I propose to make it possible with following configuration {code}
>               <outputFile>${project.build.directory}/unix-classpath.txt</outputFile>
>               <pathSeparator>:</pathSeparator>
>               <fileSeparator>/</fileSeparator>
>               <prefix>repository</prefix>
>               <useRepositoryLayout>true</useRepositoryLayout>
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)