Simulation/branch mode

Hi there,

First of all thanks for putting the effort into producing such a product. I feel tempted to contribute if I did have sufficient time and need for it.

However, two quick questions.

1) How well does Sonar handle branch of the same product. So far I haven't experimented much, but it seems to only recognize groupId+artifactId as the project identifier. That must make it hard to measure quality on trunk and branches, for those of us who use both at the same time.

2) Simulation mode

I was thinking. We sometimes want to identify if certain changes would improve or not the overall quality of the build before we check it in. The reasoning is, that often when the project is checked in, developers focus on the next task ahead. If we had the ability to show potential impact, it would be easier for the developer to go the last mile. Especially when we want to encourage a peer review development model.

Is there anyway a measure could be not committed in the DB, but a diff created in any way? I assume the answer is no, but a bit more elaborated :-)

Regards,

/Niels