[
https://issues.apache.org/jira/browse/MDEPLOY-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248418#comment-17248418
]
Robert Scholte commented on MDEPLOY-280:
----------------------------------------
I would expect specialized packaging lifecycles that don't define the install
and deploy phase. Or am I missing something?
To me it would make more sense to solve this at the plugin that attaches the
artifact, because now both both install and deploy need this kind of fix.
That's a sign for me that this is solved at the wrong spot.
> 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)
