maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MDEP-488) Build-classpath for maven repository layout
Date Thu, 08 Dec 2016 21:28:58 GMT


Robert Scholte commented on MDEP-488:

The documentation of {{prefix}} is: 
bq. The prefix to prepend on each dependent artifact. If undefined, the paths refer to the
actual files store in the local repository (the stripVersion parameter does nothing then).

This doesn't seem to be true. So we have 2 options: fix according to docs or apply your fix
+  adjust the documentation. I've been looking if this could be fixed without introducing
a new parameter, but haven't found a solution yet. 

> Build-classpath for maven repository layout
> -------------------------------------------
>                 Key: MDEP-488
>                 URL:
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: build-classpath
>    Affects Versions: 2.10
>            Reporter: Gaƫl Lalire
>         Attachments: classpathPatch.diff
> Build-classpath cannot create a classpath for a maven repository layout in multimodules
> 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
> I propose to make it possible with following configuration {code}
>               <outputFile>${}/unix-classpath.txt</outputFile>
>               <pathSeparator>:</pathSeparator>
>               <fileSeparator>/</fileSeparator>
>               <prefix>repository</prefix>
>               <useRepositoryLayout>true</useRepositoryLayout>
> {code}

This message was sent by Atlassian JIRA

View raw message