-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sonarqube-.net links in README broken #509
Comments
I'll look into this. Likely broken due to moving project location.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Daniel Doubrovkine (dB.) @dblockdotorg <[email protected]>
Sent: Saturday, March 11, 2017 1:46:24 PM
To: Waffle/waffle
Cc: Subscribed
Subject: [Waffle/waffle] sonarqube-java and sonarqube-.net links in README broken (#509)
Not sure where these should point to.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#509>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA7ho_zoNXIjI5SEoYSCol1RlxAB4vbaks5rkuwAgaJpZM4MaSx3>.
|
Java one was fixed. Originally sonar did this for us. After move, this seemed to break. The java one had a different path now but very similar. I fixed it but it had not scanned over there since the original beta in that program. Looked at how to setup and setup what I think is right but now fails on my fork so will hold off sending. In the meantime while doing this sonar website stopped responding so they may be doing maintenance. For the .net side, I think when I added an early pom module to kick off build so I didn't have to keep drilling into other files resulted in sonar seeing project fully as java and likely deleting the .net piece. Just a guess but if there is a plan to split out C## code entirely, then likely that can wait to be addressed with #510 |
OK - figured out at least temporary loading on java side. It's done on the client end on my machine. Results have been updated as of 1.9.0 branch master. I had to remove comments on sonar as way back when it didn't seem needed but now there is no matching version at latest so it requires mentioning proper sonar version. Still not sure what to do on .net side. |
Not sure where these should point to.
The text was updated successfully, but these errors were encountered: