|
the "Maven 1.x like" global dashboard for
What you want is the same dashboard as Maven 1 ? i don't understand this item "Why does the config file have to be on the compile classpath? Config files in other maven plugins are given as absolute or relative paths." Can you be more precise ? To be precise. What I would like is the ability in the config file to choose which columns are displayed in the Maven 1 style dashboard, instead of all columns for each goal-based sub-section. So I can choose to display checkstyle errors only, from the checktyle plugin, and not all of the checkstyle columns, if I want.
The idea is that the dashboard display can be trimmed down to display a small set of useful and relevant information, at-a-glance. As I have neither the will nor the time to create a "Maven 1 like" dashboard strictly identical to that of Maven 1, I advise you to use:
http://mojo.os.xebia.com/maven-dashboard-plugin/index.html The next snapshot release will implement an expand/collapse function to hide or not each plugin section. I will continue to improve the "Maven 1 like" dashboard by adding new plugin support. Best regards deployed the 2008-06-25 as 1.0-SNAPSHOT
|
||||||||||||||||||||||||||||||||||||||||||||||
The Maven 1 changes for
MOJO-847are extremely welcome, and means that I can start using this plugin to good effect.Things I'd like to see:
The ability to turn off the drill down into the fancy Maven 2 dashboard graphs. Who cares what the distribution of errors/warnings on the fancy 3d pie chart is. I suppose it does not cause any harm to leave it in.
Ability to refine the columns in the global Maven 1 style overview. For example, I'd like to be able to cut it down to Num tests, % passed, Num lines code, % covered by tests, num checkstyle errors, and that is about it. Obviously others will have their preferences.
Why does the config file have to be on the compile classpath? Config files in other maven plugins are given as absolute or relative paths.