Be able to profile a maven build

Jerome Lacoste added a comment - 27/Jan/11 8:30 AM For those who are interested in this feature: hudson already does this for you (at least in the maven3 support). the time for the mojos is stored in the build.xml (Search for ExecutedMojo). There's also a per module page summary on hudson that will display time used per mojo you can implement the same in maven by looking at http://maven.apache.org/ref/3.0.2/maven-core/apidocs/org/apache/maven/execution/AbstractExecutionListener.html . This is used in and ./maven-embedder/src/main/java/org/apache/maven/cli/ExecutionEventLogger.java and instantiated by maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java You might for example want to add a new 'profiling' option. Not to confuse with maven profiles.. if you are interested by the downloads time, you might want to look at ./maven-embedder/src/main/java/org/apache/maven/cli/AbstractMavenTransferListener.java but as downloads might happen in parallel, I am not sure you will get the information you want (i.e. user time spent waiting for download to complete) Hope that helps.

Alexander Klimetschek added a comment - 19/Mar/13 9:56 AM I implemented this - see attached patch or the diff in my github maven fork . Output looks like this at the end of the build (running "mvn -a install" for maven itself): [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:55.148s [INFO] Finished at: Tue Mar 19 15:50:33 CET 2013 [INFO] Final Memory: 29M/102M [INFO] ------------------------------------------------------------------------ [INFO] MOJO EXECUTION TIMES [INFO] ------------------------------------------------------------------------ [INFO] 35% maven-surefire-plugin [40.74s] [INFO] * test [INFO] 23% animal-sniffer-maven-plugin [27.65s] [INFO] * check [INFO] 13% project setup [15.85s] [INFO] 7% maven-assembly-plugin [8.83s] [INFO] * single [INFO] 4% maven-jar-plugin [4.86s] [INFO] * jar [INFO] 3% maven-compiler-plugin [4.21s] [INFO] * compile 3% [4.10s] [INFO] * testCompile 0% [0.11s] [INFO] 3% maven-remote-resources-plugin [4.12s] [INFO] * process [INFO] 3% plexus-component-metadata [3.49s] [INFO] * generate-metadata 2% [2.65s] [INFO] * generate-test-metadata 0% [0.85s] [INFO] 1% modello-maven-plugin [1.56s] [INFO] * java 0% [1.13s] [INFO] * xpp3-reader 0% [0.20s] [INFO] * xpp3-writer 0% [0.15s] [INFO] * xpp3-extended-reader 0% [0.08s] [INFO] 0% maven-site-plugin [1.10s] [INFO] * attach-descriptor [INFO] 0% other [0.78s] [INFO] 0% maven-resources-plugin [0.71s] [INFO] * resources 0% [0.45s] [INFO] * testResources 0% [0.25s] [INFO] 0% scanning for projects [0.71s] [INFO] 0% buildnumber-maven-plugin [0.61s] [INFO] * create-timestamp 0% [0.39s] [INFO] * create 0% [0.22s] [INFO] 0% maven-install-plugin [0.35s] [INFO] * install [INFO] ------------------------------------------------------------------------ Details from the commit message: adds new option "-a / --analyze" to the maven cli which will profile mojo executions and output their time and percentage of total time sorted at the end of the build groups by maven plugin and shows measurements split up by plugin goals also measures project discovery ("scanning"), project setup time before first mojo ("project setup") and anything else ("other") implemented in a special ExecutionListener called ProfilingExecutionListener which is chained with the normal ExecutionEventLogger by a new ExecutionListenerChain helper that forwards the events to multiple listeners WDYT?