[jira] (MNG-4639) Be able to profile a maven build

["Rod Woo (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342568#comment-342568 ] 

Rod Woo commented on MNG-4639:
------------------------------

Another option is EventSpy. EventSpy is a standard way to extend Maven so you can use it with Jenkins/Hudson and so on.

Use-Dmaven.ext.class.path=... or <maven>/lib/ext/<yours>.jar to let Maven know that you provided an extension. 

You can easily take the code of Alexander Klimetschek and make an EventSpy out of it.



> Be able to profile a maven build
> --------------------------------
>
>                 Key: MNG-4639
>                 URL: https://jira.codehaus.org/browse/MNG-4639
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>            Reporter: Baptiste MATHUS
>             Fix For: Issues to be reviewed for 3.x
>
>         Attachments: 0001-MNG-4639-Be-able-to-profile-a-maven-build.patch
>
>
> A common problem with builds is that they can become quite long to run. As it is a know anti-pattern for CI for example, one has the need to try and optimize their builds.
> The thing is: the current granularity isn't sufficiently precise. In fact, you only only the time spent to build each module. This is a good start, though.
> Maven currently displays something like the following (let's speak only about maven 3):
> {quote}
> [INFO] Reactor Summary:
> [INFO] ------------------------------------------------------------------------
> [INFO] p1 ........................ SUCCESS [1:12.938s]
> [INFO] p2 ........................ SUCCESS [5.750s]
> [INFO] p3 ........................ SUCCESS [3:58.488s]
> [INFO] p4 ........................ SUCCESS [24.437s]
> [INFO] p5 ........................ SUCCESS [1.563s]
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 46 seconds
> {quote}
> What would be great would be adding an option that would higher the details. Something like -A/--analyze (--profile would be too close to -P/profile option) would add detailed analysis, would print something like. 
> {quote}
> [INFO] Reactor Summary:
> [INFO] ------------------------------------------------------------------------
> [INFO] p1 ........................ SUCCESS [1:12.938s]
>         clean:clean (somepkg.CleanMojo) : 10.3s
>         compiler:compile (...) : 50s
>         ...
>         and so on
> {quote}
> I'm not very well aware the level of details maven 3 API could provide. So the printing above could become irrelevant. In this case, printing a dedicated html or so report might be a better choice.
> Cheers
> PS : Though I'm really not introduced into maven code, if you think it's not too complicated, I could try and contribute on this field if I'm given some hints or good starting points. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)