|
multimodule metrics twice
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Hello Nino, What version of Sonar do you use ? Can you tell me as well what date (last build) appears in the dashboards of various modules ? Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Olivier It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino 2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Hello Nino, I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ? Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Hi Olivier Ok, i'll do so. 2009/10/16 Olivier Gaudin <gaudol@...>
Hello Nino,
I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ?
Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Hello Nino, I have received your sample project and have run Sonar on it. I do not see duplications of modules. Here is what I think happens : prior to 1.11, Sonar can get confused when switching modules around. I think that upgrading to 1.11 should resolve your issue.
Olivier
On Mon, Oct 19, 2009 at 9:27 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
Ok, i'll do so.
2009/10/16 Olivier Gaudin <gaudol@...>
Hello Nino,
I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ?
Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Hi again Oliver I've upgraded to sonar 1.11, still seems strange.. Common reports the aggregated numbers of flowcontrol and iocconfiguration (it's two subprojects). Like so, http://img18.imageshack.us/img18/4571/sonarb.png
It might just be that it's working now, it seems very strange that I have several duplicated entries in the same file and lines? Although I do not see the source files twice as earlier on.
2009/10/19 Olivier Gaudin <gaudol@...>
Hello Nino,
I have received your sample project and have run Sonar on it. I do not see duplications of modules.
Here is what I think happens : prior to 1.11, Sonar can get confused when switching modules around. I think that upgrading to 1.11 should resolve your issue.
Olivier
On Mon, Oct 19, 2009 at 9:27 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
Ok, i'll do so.
2009/10/16 Olivier Gaudin <gaudol@...>
Hello Nino,
I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ?
Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Cool ! The duplication is standard behavior. If A duplicates B, Sonar shows a duplication from A to B and a duplication from B to A. If A duplicates A, Sonar shows a duplication from A to A and from A to A again.
Olivier
On Mon, Oct 19, 2009 at 2:58 PM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi again
Oliver I've upgraded to sonar 1.11, still seems strange.. Common reports the aggregated numbers of flowcontrol and iocconfiguration (it's two subprojects). Like so,
http://img18.imageshack.us/img18/4571/sonarb.png
It might just be that it's working now, it seems very strange that I have several duplicated entries in the same file and lines? Although I do not see the source files twice as earlier on.
2009/10/19 Olivier Gaudin <gaudol@...>
Hello Nino,
I have received your sample project and have run Sonar on it. I do not see duplications of modules.
Here is what I think happens : prior to 1.11, Sonar can get confused when switching modules around. I think that upgrading to 1.11 should resolve your issue.
Olivier
On Mon, Oct 19, 2009 at 9:27 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
Ok, i'll do so.
2009/10/16 Olivier Gaudin <gaudol@...>
Hello Nino,
I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ?
Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
|
Re: multimodule metrics twice
Okay, thought so.. Thanks for helping.. 2009/10/19 Olivier Gaudin <gaudol@...>
Cool !
The duplication is standard behavior. If A duplicates B, Sonar shows a duplication from A to B and a duplication from B to A. If A duplicates A, Sonar shows a duplication from A to A and from A to A again.
Olivier
On Mon, Oct 19, 2009 at 2:58 PM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi again
Oliver I've upgraded to sonar 1.11, still seems strange.. Common reports the aggregated numbers of flowcontrol and iocconfiguration (it's two subprojects). Like so,
http://img18.imageshack.us/img18/4571/sonarb.png
It might just be that it's working now, it seems very strange that I have several duplicated entries in the same file and lines? Although I do not see the source files twice as earlier on.
2009/10/19 Olivier Gaudin <gaudol@...>
Hello Nino,
I have received your sample project and have run Sonar on it. I do not see duplications of modules.
Here is what I think happens : prior to 1.11, Sonar can get confused when switching modules around. I think that upgrading to 1.11 should resolve your issue.
Olivier
On Mon, Oct 19, 2009 at 9:27 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
Ok, i'll do so.
2009/10/16 Olivier Gaudin <gaudol@...>
Hello Nino,
I am not too sure I understand your setup. Could you send me a sample project that I can try to reproduce ?
Olivier
On Fri, Oct 16, 2009 at 8:39 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Olivier
It's v.1.10.1 of sonar.. And the build date for our modules are consistent,
2009-10-13 |
Version |
1.10-SNAPSHOT(2009-10-13) |
|
|
| 2009-10-09 |
Version |
1.10-SNAPSHOT(2009-10-09) |
|
|
| 2009-10-07 |
Version |
1.10-SNAPSHOT(2009-10-07) |
However as you can see we do not switch snapshot version often, could that be trouble? And I manually have to go in append the build date to the version in order to get new sonar metrics in (even though it's run automatically with hudson every night). But remember that even when I deleted the project it got the metrics twice for the first sonar analysis.
Regards Nino
2009/10/15 Olivier Gaudin <gaudol@...>
Hello Nino,
What version of Sonar do you use ?
Can you tell me as well what date (last build) appears in the dashboards of various modules ?
Olivier
On Thu, Oct 15, 2009 at 8:58 AM, nino martinez wael <nino.martinez.wael@...> wrote:
Hi Im
Using sonar with maven on a java project. Our maven project layour looks
like this:
Parent (pom project)
|-javaproject
|
|-common (pom project)
|-Java project
|-Java project
Now it seems that sonar are picking up sources under common (one for common
and then for the seperate sub projects) twice thus reporting twice for it,
and also giving metrics twice. We initially did not have this layout, common
itself were a java project a refatoring made the switch. I've tried deleting
the project from sonar, that makes no change (except that all our history
are gone so it does delete the data). I've also tried filling in common in
exclude modules (sonar.skippedmodules) but that ignores common and
subprojects..
Is there a way to fix this or am I doing something wrong?
PS im really happy with sonar other than above...
regards Nino
|
