[jira] [Commented] (MNG-6302) Provide some "progress" hints

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user rmannibucau opened a pull request:

    https://github.com/apache/maven/pull/136

    [MNG-6302] logging the module count

    Idea is to let the user identify how many modules are still to be executed/processed

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmannibucau/maven fb/MNG-6302_module-progress

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven/pull/136.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #136
    
----
commit 4d49d3b05b2e3d3a4530bb27e8cc162ab50baa7c
Author: Romain Manni-Bucau <rm...@gmail.com>
Date:   2017-11-09T08:30:47Z

    logging the module count to let the user identify how many module are still to be executed/processed

----


> Provide some "progress" hints
> -----------------------------
>
>                 Key: MNG-6302
>                 URL: https://issues.apache.org/jira/browse/MNG-6302
>             Project: Maven
>          Issue Type: New Feature
>            Reporter: Romain Manni-Bucau
>
> High level need is to know when you launched a "long"/"big" build where you are without having to scroll for days. Some progress information would be neat.
> A proposal is to add the info in term of module number of total number of modules after the artifact logging like:
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Foo 1.0.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] Module 10 / 100
> {code}
> If it can be more fancy it would be appreciated but this simple solution looks good enough to fulfill the original requirement.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)