Skip to content
This repository has been archived by the owner on Jan 7, 2021. It is now read-only.

Overview Comment is not being reset with '-Dsonar.stash.comments.reset=true' #119

Open
tknerr opened this issue Apr 3, 2017 · 10 comments
Open
Assignees
Milestone

Comments

@tknerr
Copy link

tknerr commented Apr 3, 2017

I was surprised the -Dsonar.stash.comments.reset=true only resets the earlier comments in the diff, but not the overview comment.

Is this the desired behaviour, or is there something wrong on my side?

I find it surprising at least, and the the README also doesn't mention that it would relate to the diff comments only.

@t-8ch
Copy link
Contributor

t-8ch commented Apr 4, 2017

@tknerr True, this should also affect the overview comment.

@t-8ch t-8ch self-assigned this Apr 4, 2017
@t-8ch t-8ch added this to the Wishlist milestone Apr 4, 2017
@sebastian-r
Copy link

Hi,

do you have an idea when this will be integrated ?

@t-8ch
Copy link
Contributor

t-8ch commented Nov 1, 2017

I was working on it today.
The problem is, that the overview comments has to be requested with a new API endpoint, which we currently don't use.
I used this to also implement a generic accessor for paged API endpoints.
A first prototype should be done tomorrow.

@sebastian-r
Copy link

Awesome, thank you!

@t-8ch
Copy link
Contributor

t-8ch commented Nov 3, 2017

@sebastian-r Can you take a look at #162?

@sebastian-r
Copy link

Hi @t-8ch ,

sorry I am responding so late. Had holiday and trainings. I will have a look at it tomorrow. Thanks already for your engagement :)

@t-8ch
Copy link
Contributor

t-8ch commented Jan 30, 2018

Hi @sebastian-r,

any updates?

@t-8ch
Copy link
Contributor

t-8ch commented Jan 30, 2018

@tknerr , Could you also validate this?

@tknerr
Copy link
Author

tknerr commented Jan 30, 2018

@t-8ch sorry don't have that sonar instance available anymore (different project, different toolchain.... :-/)

@tonyfalabella
Copy link

You can look at the change in this PR and manually apply it and build your own jar with the change included: #162
Unfortunately it was for an older codebase (I believe 1.3.0 and current release is 1.6.0) and as such you'll manually have to apply that fix against the latest codebase you'd like. I've used the fix provided and it works nicely against 1.51.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants