|
ok
deployed as new snpahot version dashboard-maven-plugin-1.0-20080310.203128-18.jar I tested the new snapshot, and found that it works when new data was added. However, my old data is not incorporated correctly when the version has changed. Thus I would request that the issue is reopened. It would be an improvement if the data saving part is kept the same as before, and only change the query for data . This way, you could easily switch between the two modes (keepVersionAsDiscriminant = true or false) without having to change the data.
As Odin Standal added a comment, i reopen this issue to take account his approach
The new parameter "keepVersionAsDiscriminantCriteria" will work at querying data and no at storing data as Odin Standal's proposition and help
desployed the 2008-04-05 as 1.0-SNAPSHOT ( dashboard-maven-plugin-1.0-20080405.182352-19.jar)
Hello,
Thanks for adding the new parameter. Displaying the progress between different project versions on the same chart is exactly what I needed. I have only one remark: The history for previous versions still misses in the dashboard of a multimodule project. In my organization we have all internally developed modules of an application developed under the same svn directory. For example: svn/trunk/MyApplication: And by convention all those projects including the parent one (the pom.xml file directly under the svn/trunk/MyApplication directory) have the same version number which changes between different releases. Is it possible to have the history of different versions of the parent project in the same chart? Best regards, HI,
i don't understand your request. If you configure the dashboard in pom.xml of svn/trunk/MyApplication project and add each application as sub-module of this you can make at root level (svn/trunk/MyApplication) :
and for the parent and each sub-module, you have an historic report with version progress ? Overlapping version numbers on the historical chart.
Hi David,
Sorry. Maybe I've made an error yesterday while generating the historical dashboard. But now the historical dashboard for th parent project looks fine. I attached the surefire historical chart for one of my the parent projects. P.S. Maybe, one possible improvement would be to vary the level on which the version numbers are displayed to avoid that they overlap. Something like: I........................................................I Version 1.0..........................I Version 1.1 Or maybe you would have a better idea. Anyway, I am happy with the historical charts as they are displayed now, because I can see the project evolution between different releases. Best thanks, Hi Venelin,
i'm happy to see that it works fine for you. For the label marker overlapping, i'm working on it. It's not beautiful |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Major
Add a new parameter to avoid "loosing the history" after changing a project's version
)
The <keepVersionAsDiscriminantCriteria> parameter will be used to keep the version as a discriminant criteria of a project.
If set as "true", the data of reports will be specific to this version of a project.
If set as "false", the data of reports will be associated with the project regardless of its version.
By default, the <keepVersionAsDiscriminantCriteria> parameter will be set to "true"
Best regards
David