Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/khmarbaise/maven-buildtime-profiler
Maven Build Time Profiler
https://github.com/khmarbaise/maven-buildtime-profiler
java maven maven-extension
Last synced: about 2 months ago
JSON representation
Maven Build Time Profiler
- Host: GitHub
- URL: https://github.com/khmarbaise/maven-buildtime-profiler
- Owner: khmarbaise
- License: apache-2.0
- Created: 2016-01-11T11:12:25.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2023-11-16T11:23:32.000Z (about 1 year ago)
- Last Synced: 2024-10-16T20:21:08.581Z (2 months ago)
- Topics: java, maven, maven-extension
- Language: Java
- Homepage: https://khmarbaise.github.io/maven-buildtime-profiler
- Size: 868 KB
- Stars: 69
- Watchers: 7
- Forks: 12
- Open Issues: 18
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Maven BuildTime Profiler
[](http://www.apache.org/licenses/)
[](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.soebes.maven.extensions%22%20a%3A%22maven-buildtime-profiler%22)
[](https://cloud.drone.io/khmarbaise/maven-buildtime-profiler)
Often you have the problem that in large builds, you need to find
where time is consumed.
This is an [EventSpy][1] implementation which collects all the information of
all phases and mojo executions and make a summarization output at the end of
the build.
If you like to use this EventSpy with Maven 3.1.1+ till Maven 3.2.5 you need
to manually download it from Maven Central and put the resulting jar
file into the `${M2_HOME}/lib/ext` directory or if you
like to use it directly you have to add the following parameter on command line:
```
mvn -Dmaven.ext.class.path=PathWhereItIsLocated/maven-buildtime-profiler-0.2.0-mvn311.jar clean package
```
If you like to use this extension for Maven 3.3.1+ you
have to define the following `.mvn/extensions.xml` file:
``` xml
com.soebes.maven.extensions
maven-buildtime-profiler
0.2.0
```
The download from Maven Central will be done by Maven itself.
Here's an example of what the output will look like:
```
[INFO] ------------------------------------------------------------------------
[INFO] -- Maven Build Time Profiler Summary --
[INFO] ------------------------------------------------------------------------
[INFO] Project discovery time: 85 ms
[INFO] ------------------------------------------------------------------------
[INFO] Project Build Time (reactor order):
[INFO]
[INFO] parse-pom:
[INFO] 169 ms : clean
[INFO] 457 ms : process-resources
[INFO] 663 ms : compile
[INFO] 14 ms : process-test-resources
[INFO] 197 ms : test-compile
[INFO] 1109 ms : test
[INFO] 1105 ms : package
[INFO] 811 ms : integration-test
[INFO] 53 ms : verify
[INFO] ------------------------------------------------------------------------
[INFO] Lifecycle Phase summary:
[INFO]
[INFO] 169 ms : clean
[INFO] 457 ms : process-resources
[INFO] 663 ms : compile
[INFO] 14 ms : process-test-resources
[INFO] 197 ms : test-compile
[INFO] 1109 ms : test
[INFO] 1105 ms : package
[INFO] 811 ms : integration-test
[INFO] 53 ms : verify
[INFO] ------------------------------------------------------------------------
[INFO] Plugins in lifecycle Phases:
[INFO]
[INFO] clean:
[INFO] 169 ms: org.apache.maven.plugins:maven-clean-plugin:3.0.0:clean (default-clean)
[INFO] process-resources:
[INFO] 457 ms: org.apache.maven.plugins:maven-resources-plugin:2.7:resources (default-resources)
[INFO] compile:
[INFO] 663 ms: org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile)
[INFO] process-test-resources:
[INFO] 14 ms: org.apache.maven.plugins:maven-resources-plugin:2.7:testResources (default-testResources)
[INFO] test-compile:
[INFO] 197 ms: org.apache.maven.plugins:maven-compiler-plugin:3.3:testCompile (default-testCompile)
[INFO] test:
[INFO] 1109 ms: org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test)
[INFO] package:
[INFO] 871 ms: org.apache.maven.plugins:maven-assembly-plugin:2.6:single (make-executable-jar)
[INFO] 234 ms: org.apache.maven.plugins:maven-jar-plugin:2.6:jar (default-jar)
[INFO] integration-test:
[INFO] 811 ms: org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:integration-test (failsafe-integration-test)
[INFO] verify:
[INFO] 53 ms: org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (failsafe-verify)
[INFO] ------------------------------------------------------------------------
[INFO] ForkTime: 0
```
Most important might be in this relationship that you will get also informations about the
time taken to install artifacts:
```
[INFO] ------------------------------------------------------------------------
[INFO] Installation summary:
[INFO] 0 ms : com.soebes.examples.j2ee:service:1.1.2-SNAPSHOT:pom
[INFO] 1 ms : com.soebes.examples.j2ee:parent:1.1.2-SNAPSHOT:pom
[INFO] 5 ms : com.soebes.examples.j2ee:shade:1.1.2-SNAPSHOT:test:jar
[INFO] 1 ms : com.soebes.examples.j2ee:service-client:1.1.2-SNAPSHOT:pom
[INFO] 0 ms : com.soebes.examples.j2ee:domain:1.1.2-SNAPSHOT:pom
[INFO] 3 ms : com.soebes.examples.j2ee:webgui:1.1.2-SNAPSHOT:pom
[INFO] 1 ms : com.soebes.examples.j2ee:service:1.1.2-SNAPSHOT:jar
[INFO] 0 ms : com.soebes.examples.j2ee:service-client:1.1.2-SNAPSHOT:jar
[INFO] 1 ms : com.soebes.examples.j2ee:domain:1.1.2-SNAPSHOT:jar
[INFO] 10 ms : com.soebes.examples.j2ee:assembly:1.1.2-SNAPSHOT:archive:zip
[INFO] 19 ms : com.soebes.examples.j2ee:assembly:1.1.2-SNAPSHOT:prod:jar
[INFO] 6 ms : com.soebes.examples.j2ee:shade:1.1.2-SNAPSHOT:dev:jar
[INFO] 6 ms : com.soebes.examples.j2ee:shade:1.1.2-SNAPSHOT:prod:jar
[INFO] 1 ms : com.soebes.examples.j2ee:shade:1.1.2-SNAPSHOT:pom
[INFO] 6 ms : com.soebes.examples.j2ee:assembly:1.1.2-SNAPSHOT:dev:jar
[INFO] 1 ms : com.soebes.examples.j2ee:assembly:1.1.2-SNAPSHOT:pom
[INFO] 0 ms : com.soebes.examples.j2ee:appasm:1.1.2-SNAPSHOT:pom
[INFO] 2 ms : com.soebes.examples.j2ee:webgui:1.1.2-SNAPSHOT:war
[INFO] 8 ms : com.soebes.examples.j2ee:app:1.1.2-SNAPSHOT:pom
[INFO] 1 ms : com.soebes.examples.j2ee:shade:1.1.2-SNAPSHOT:jar
[INFO] 3 ms : com.soebes.examples.j2ee:app:1.1.2-SNAPSHOT:ear
[INFO] 75 ms 34,888,754 bytes. 443.633 MiB / s
```
And much more important are things like the time for the deployment:
```
[INFO] ------------------------------------------------------------------------
[INFO] Deployment summary:
[INFO] 19 ms : com.soebes.examples.j2ee:assembly:1.1.2-20160306.145402-11:pom
[INFO] 20 ms : com.soebes.examples.j2ee:service-client:1.1.2-20160306.145401-11:jar
[INFO] 80 ms : com.soebes.examples.j2ee:assembly:1.1.2-20160306.145402-11:prod:jar
[INFO] 20 ms : com.soebes.examples.j2ee:shade:1.1.2-20160306.145402-11:pom
[INFO] 19 ms : com.soebes.examples.j2ee:shade:1.1.2-20160306.145402-11:jar
[INFO] 84 ms : com.soebes.examples.j2ee:webgui:1.1.2-20160306.145401-11:war
[INFO] 20 ms : com.soebes.examples.j2ee:service:1.1.2-20160306.145401-11:jar
[INFO] 192 ms : com.soebes.examples.j2ee:assembly:1.1.2-20160306.145402-11:archive:zip
[INFO] 79 ms : com.soebes.examples.j2ee:shade:1.1.2-20160306.145402-11:prod:jar
[INFO] 20 ms : com.soebes.examples.j2ee:webgui:1.1.2-20160306.145401-11:pom
[INFO] 23 ms : com.soebes.examples.j2ee:service-client:1.1.2-20160306.145401-11:pom
[INFO] 90 ms : com.soebes.examples.j2ee:shade:1.1.2-20160306.145402-11:dev:jar
[INFO] 38 ms : com.soebes.examples.j2ee:domain:1.1.2-20160306.145401-11:jar
[INFO] 19 ms : com.soebes.examples.j2ee:appasm:1.1.2-20160306.145402-11:pom
[INFO] 18 ms : com.soebes.examples.j2ee:app:1.1.2-20160306.145401-11:pom
[INFO] 103 ms : com.soebes.examples.j2ee:assembly:1.1.2-20160306.145402-11:dev:jar
[INFO] 39 ms : com.soebes.examples.j2ee:parent:1.1.2-20160306.145401-11:pom
[INFO] 101 ms : com.soebes.examples.j2ee:shade:1.1.2-20160306.145402-11:test:jar
[INFO] 93 ms : com.soebes.examples.j2ee:app:1.1.2-20160306.145401-11:ear
[INFO] 19 ms : com.soebes.examples.j2ee:service:1.1.2-20160306.145401-11:pom
[INFO] 18 ms : com.soebes.examples.j2ee:domain:1.1.2-20160306.145401-11:pom
[INFO] 1,114 ms 34,888,754 bytes. 29.868 MiB / s
```
Prerequisites minimum for this is Maven 3.1.1+ and Java 1.8 as run time.
If you have ideas for improvements etc. just fill in issues in the tracking system.
[1]: https://maven.apache.org/ref/3.0.3/maven-core/apidocs/org/apache/maven/eventspy/AbstractEventSpy.html