[
https://issues.apache.org/jira/browse/MDEPLOY-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965716#comment-17965716
]
Olivier Lamy commented on MDEPLOY-156:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#165|https://github.com/apache/maven-deploy-plugin/issues/165].
> Add flag to 'ignoreReleaseDeployErrors' to ease multi module release builds
> with classifiers.
> ---------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-156
> URL: https://issues.apache.org/jira/browse/MDEPLOY-156
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Dominik Richner
> Assignee: Robert Scholte
> Priority: Major
> Attachments: ignoreDeployErrors.patch
>
>
> Add a parameter to allow ignoring deployment errors for release artifacts,
> this is helpful if you'r releasing a multimodule project from a tag, where
> some modules are deployed with different classifiers and you let it to the
> repository manager to decide which ones can be deployed or not (a good repo
> manager blocks deployments of the same artifact with the same release
> version, but different classifiers are allowed). By using this flag one does
> not have to fiddle with the 'skip' flag, but lets the remote repository to
> make the decision. Therefore the idea is to have a kind of an automated
> 'skip' mode.
> In our usecase we have a project with more then 40 modules and multiple
> profiles for about 10 of the modules. Each profile will create the
> corresponding artifact (not every) with a new classifier. Therefore, until
> all modules are deployed, the build has to be triggered about 10 times. IN
> this scenario, the build manager should not have to care about which of the
> modules have to be build in a separate build, but should be able to trigger
> the whole build with from the top level and maven/infrastructure should take
> care about which artifacts is allowed/must be deployed to the repository
> manager.
> Note: as SNAPSHOTs can be overwritten in any case, there is no sense in
> having the same for SNAPSHOTs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
