2013/1/10 Gilles Sadowski <gil...@harfang.homelinux.org>: > On Wed, Jan 09, 2013 at 09:23:26PM +0100, Olivier Lamy wrote: >> 2013/1/9 Gilles Sadowski <gil...@harfang.homelinux.org>: >> > On Wed, Jan 09, 2013 at 04:46:43PM +0100, Olivier Lamy wrote: >> >> 2013/1/9 Olivier Lamy <ol...@apache.org>: >> >> > 2013/1/9 Gilles Sadowski <gil...@harfang.homelinux.org>: >> >> >> Hi. >> >> >> >> >> >>> >> [...] >> >> >>> >> > Note: currently some content is imported which could be removed >> >> >>> >> > (I >> >> >>> >> > think about cobertura for modules which use sonar). >> >> >>> >> > >> >> >>> >> > What is the status about moving cobertura to a dedicated profile >> >> >>> >> > in >> >> >>> >> > parent pom ? >> >> >>> >> > Can I move it to a reporting profile in parent pom ? >> >> >>> >> > >> >> >>> > >> >> >>> > For [Math] it would be much better (since AFAIK nobody came up with >> >> >>> > a way to >> >> >>> > disable Cobertura on a per-component basis). >> >> >>> > >> >> >>> > From what I infer from looking at the Sonar report page, we could >> >> >>> > have the >> >> >>> > best of all worlds if every Commons project were registered >> >> >>> > indepently in >> >> >>> > Sonar. Currently, there is one "Commons Proper Aggregator Project >> >> >>> > 1.0-SNAPSHOT" (which does not represent the actual situation that >> >> >>> > the >> >> >>> > components are independent from each other). However, it seems that >> >> >>> > with >> >> >>> > several projects registered, it could be possible to compare two >> >> >>> > versions >> >> >>> > of the same project, thereby providing complete information on the >> >> >>> > evolution >> >> >>> > of the code. Am I wrong? >> >> >>> >> >> >>> Something like >> >> >>> https://analysis.apache.org/dashboard/index/org.apache.commons:commons-exec >> >> >>> or >> >> >>> https://analysis.apache.org/dashboard/index/org.apache.commons:commons-math3 >> >> >>> ? >> >> >> >> >> >> What I'd like to be clear on the report page is the release versions >> >> >> (of >> >> >> Commons Math): the timelines always refer to a non-existent >> >> >> "1.0-SNAPSHOT". >> >> >> See e.g. >> >> >> https://analysis.apache.org/dashboard/index/122571?did=4&period=3 >> >> >> >> >> > >> >> > I see (this generates extra maintenance on analysis.a.o as I need to >> >> > created a job per project) >> >> > But I will >> >> done see: >> >> https://analysis.apache.org/dashboard/index/org.apache.commons:commons-math3 >> > >> > Thanks. >> > Will there be something to be done for each release, or is there some >> > automagic link between sonar and Jira (or SVN?) that can remember when some >> > release happened and add the little triangle? >> Not sure of that but it looks sonar detect versions from pom. >> As sample see https://analysis.apache.org/dashboard/index/35142?did=4 > > That's close, but the ideal would be that official release also appear in > the tables. And that will not happen by reading the pom file because there, > the version is always in the form "x.y[.z]-SNAPSHOT". > > Would it be possible to request a "one-time" analysis by pointing Sonar to > the SVN tag of the new official release? [And have that analysis inserted in > the time-line of course ;-).] > on request only :-) > > Best regards, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
