[
https://issues.apache.org/jira/browse/SCM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959857#comment-17959857
]
ASF GitHub Bot commented on SCM-268:
------------------------------------
jira-importer opened a new issue, #257:
URL: https://github.com/apache/maven-scm/issues/257
**[Roald
Bankras](https://issues.apache.org/jira/secure/[email protected])**
opened
**[SCM-268](https://issues.apache.org/jira/browse/SCM-268?redirect=false)** and
commented
In a multi module project, the tagging of a successful build should only
occur after all modules have completed their build cycle. Therefor, I propose
to make the scm:tag mojo an aggregator. Thus forcing it to run in a separate
task segment.
---
**Attachments:**
-
[MPSCM-95-scm.patch](https://issues.apache.org/jira/secure/attachment/12718833/MPSCM-95-scm.patch)
(_492 bytes_)
**Issue Links:**
- [SCM-297](https://issues.apache.org/jira/browse/SCM-297) scm:tag process
child poms recursively and attempts to tag submodules
> Add aggregator annotation to the tag mojo
> -----------------------------------------
>
> Key: SCM-268
> URL: https://issues.apache.org/jira/browse/SCM-268
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-plugin
> Reporter: Roald Bankras
> Assignee: Emmanuel Venisse
> Priority: Major
> Attachments: MPSCM-95-scm.patch
>
>
> In a multi module project, the tagging of a successful build should only
> occur after all modules have completed their build cycle. Therefor, I propose
> to make the scm:tag mojo an aggregator. Thus forcing it to run in a separate
> task segment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
