You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gordon Pettey (JIRA)" <ji...@apache.org> on 2017/06/29 14:54:00 UTC
[jira] [Commented] (MDEP-574) include not matching for custom types
[ https://issues.apache.org/jira/browse/MDEP-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068436#comment-16068436 ]
Gordon Pettey commented on MDEP-574:
------------------------------------
"Puring artifact: g:a:t:v"
Looks like another thing that needs to be considered for determining a standard order for G:A:V:[PT]:C.
> include not matching for custom types
> -------------------------------------
>
> Key: MDEP-574
> URL: https://issues.apache.org/jira/browse/MDEP-574
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: purge-local-repository
> Affects Versions: 3.0.1
> Environment: Win 7, 64 Bit, JDK 8u92, MVN 3.5.0, MDEP 3.0.1
> Reporter: Markus Karg
>
> Apparently MDEP's purge-local-repository cannot explicitly include dependencies with custom types, like "de.quipsy:qsstatoleobject-pbd:pbd", because (according to the javadocs of private String gavToPath( String gav )) the goal's private coordiante parser expects g:a:v, while the actual coordinates of this include are g:a:t:v.
> Effectively this render <include> not mathing anything.
> Workaround: Do not use includes, but simply purge ALL dependencies (in this case, the artifact is correctly found, and in debug mode also is correctly reported as "Puring artifact: g:a:t:v".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)