[
https://issues.apache.org/jira/browse/MDEPLOY-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965562#comment-17965562
]
Olivier Lamy commented on MDEPLOY-22:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#271|https://github.com/apache/maven-deploy-plugin/issues/271].
> distributionManagement/repository shouldn't be required
> -------------------------------------------------------
>
> Key: MDEPLOY-22
> URL: https://issues.apache.org/jira/browse/MDEPLOY-22
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Matthew Beermann
> Assignee: Brett Porter
> Priority: Major
>
> Currently, the deploy plugin will blow up if there isn't a nonempty
> <repository/> defined inside of <distrubutionManagement>. This is silly;
> there are situations where you might not need or want to deploy your files to
> a remote repository. Right now, for eample, I'm trying to set up a
> documentation-only build - I'm only interested in the reports. I don't see
> any real reason to require this element.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
