[
https://issues.apache.org/jira/browse/MDEPLOY-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965584#comment-17965584
]
Olivier Lamy commented on MDEPLOY-89:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#254|https://github.com/apache/maven-deploy-plugin/issues/254].
> Skip won't work if distribution management is not specified
> -----------------------------------------------------------
>
> Key: MDEPLOY-89
> URL: https://issues.apache.org/jira/browse/MDEPLOY-89
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: René Link
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 2.5
>
>
> Imagine a project where you want to adjust the standard build lifecycle of a
> packaging type. You want to do most of the build steps as definied by the
> packacking type except the deployment. You want to a let your own plugin do
> the work. In this case you have to skip the deploy goal of the deploy plugin.
> It is possible to set the skip property of the deploy plugin to true, but
> this will cause an error if you haven't specified a distribution management.
> The problem:
> The deploy plugin defines the property deploymentRepository
> (http://maven.apache.org/plugins/maven-deploy-plugin/xref/org/apache/maven/plugin/deploy/DeployMojo.html#85).
> Because of the dependency injection by plexus, plexus tries to resolve the
> ArtifactRepository which is not possible if there is no distribution
> management definied.
> I don't know much about plexus, but it should be possible to define that
> property as lazy loading. I guess this will fix the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
