You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/05/17 05:47:00 UTC

[jira] [Commented] (MNG-7883) Also print groupId and version in the Reactor Build Order

    [ https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847157#comment-17847157 ] 

ASF GitHub Bot commented on MNG-7883:
-------------------------------------

monniechuang opened a new pull request, #1511:
URL: https://github.com/apache/maven/pull/1511

   **JIRA Issue**: [MNG-7883](https://issues.apache.org/jira/browse/MNG)
   
   **Description**:
   This pull request addresses the enhancement described in JIRA issue MNG-7883. The goal is to improve the readability and completeness of the Reactor Build Order output by including `groupId` and `version` information for each module. This change is necessary to provide developers with more detailed information about the modules being built, which can help in debugging and understanding the build process.
   
   **Changes Made**:
   - Modified the `ExecutionEventLogger` class to include `groupId` and `version` information in the Reactor Build Order output.
   - Updated the `sessionStarted` method to format the output with the new information, ensuring clarity and consistency.
   
   **Implementation Details**:
   - The `sessionStarted` method in `ExecutionEventLogger` was updated to construct a formatted string containing the `groupId`, `artifactId`, and `version` for each module.
   - Adjusted the spacing and alignment to ensure the output remains clear and readable.
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed
          for the change (usually before you start working on it).  Trivial changes like typos do not
          require a JIRA issue. Your pull request should address just this issue, without
          pulling in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[MNG-XXX] SUMMARY`,
          where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.
    - [x] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`.
          Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
    - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
          be performed on your pull request automatically.
    - [x] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> Also print groupId and version in the Reactor Build Order
> ---------------------------------------------------------
>
>                 Key: MNG-7883
>                 URL: https://issues.apache.org/jira/browse/MNG-7883
>             Project: Maven
>          Issue Type: Improvement
>          Components: Reactor and Workspace
>            Reporter: Reto Hoehener
>            Priority: Trivial
>
> This would be useful information when debugging a build process:
> {code:java}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] my-group        my-parent            1.0.0-SNAPSHOT                [pom]
> [INFO] my-group        my-lib               1.0.0-SNAPSHOT                [jar]
> [INFO] my-group        my-app               1.0.4                         [jar] {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)