how to time (profile) maven goals in a multi-module project

We have a huge project with many submodules. A full build takes currently over 30mins.

I wonder how this time distributes开发者_运维百科 over different plugins/goals, e.g. tests, static analysis (findbugs, pmd, checkstyle, etc ...)

Would it be possible to time the build to see where (in both dimensions: modules and goals) most time is spent?

The maven-buildtime-extension is a maven plugin that can be used to see the times of each goal:

https://github.com/timgifford/maven-buildtime-extension

If you run the build in a CI server like TeamCity or Jenkins (formerly Hudson), it will give you timestamps for every step in the build process and you should be able to use these values to determine which goals/projects are taking the most time.

I don't think there is any way built in to maven to do this. In fact, in the related question artbristol posted, there is a link to a Maven feature request for this functionality. Unfortunately, this issue is unresolved and I don't know if it will ever be added.

The other potential solution is to write your own plugin which would provide this build metadata for you.

I don't think there is a way to determine the timing of particular goals. What you can do is run the particular goals separately to see how long they take. So instead of doing a "mvn install" which runs all of your tests, checkstyle, etc.. just do "mvn checkstyle:checkstyle" to see how long that takes for a particular module.

Having everything done every time is nice when its done by an automated server (continuum/jenkins/hudson) but when you are building locally, sometimes its better to be able to just compile. Some of the things you can do are have the static analysis goals ONLY run when you pass in a certain parameter or profile. Another option is to only have them ran when maven.test.skip=false.

If you are using a continuous build, try having the static analysis only done every 4 hours, or daily.