[
https://issues.apache.org/jira/browse/MDEPLOY-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248420#comment-17248420
]
Tamás Cservenák commented on MDEPLOY-280:
-----------------------------------------
I agree with you, ideally, yes, this is the "producer" issue (something that
produces and attaches). The M-D-P change could be more like a "last resort"
(maybe emphasize that in parameter doco as well), something you really want to
use ONLY until the "producer" does not accept the patch someone provided :) or
does not address the issue somehow differently.
So if you use some plugin, cannot modify it immediately (to prevent attaching
something, but your build does need it's product), the possibility is still
there...
> Ability so skip certain classifiers from deploy
> -----------------------------------------------
>
> Key: MDEPLOY-280
> URL: https://issues.apache.org/jira/browse/MDEPLOY-280
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy
> Reporter: Tamás Cservenák
> Priority: Minor
>
> There are cases when producing and attaching "derivative" artifacts (docker
> image of main artifact, rpm of same, etc) is needed, but their deploy is not
> wanted, as they are either used only during ITs, and are "just derivative",
> or, they are to be deployed in their format specific registries/repositories
> instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
