Stefan Cordes

The xml plugin from sonar has some nice helpers to find the line numbers (XmlTextRange). With the original xpath boolean the location is not possible to find. I added the...

Hi @abhayagarwalonline , just a few rules are prepared to show line numbers: "HTTP Listener should use HTTPS protocol" and "HTTP Listener should use a specific port property". All others...

Just edit the rules-4.xml (and create a pull-request) ;-) Each body of the nodes has a boolean xpath. The locationHint="" needs to have "the same" rule but returning the **first...

Did you try `locationHint="//*[local-name()='listener-config']"` ?

Hi Abhay, the javax.xml.* is bundled with the jre. The implementation used should best be the one used by sonar:  which comes transient from ``` org.sonarsource.analyzer-commons sonar-xml-parsing 1.12.0.632 ```...

I created a fork with *.mule as extension which requires to copy/rename the files before analysis: https://github.com/c-a-services/mule-sonarqube-plugin/tree/use-mule-file-extension (Just changing in sonar config is not sufficient as MuleFilePredicate still searching for...

HI @fperezpa, 1. that would be a huge manual work to maintain each project (when it is firstly created we normally do not perfom manual tasks). 2. the xml plugin...

Hi @chirubtech, great tip to not disturb XML plugin using for other (non-mule) projects and avoid copying/rename mule-files. Unfortunately we currently have XML plugin rules (xpath) for mule-applications :-( When...

In the meantime I found another workaround for us: > The maven 3.9 workaround is to switch back to the (outdated) wagon protocol via -Dmaven.resolver.transport=wagon (Proposed solution is to fully...

Do you know when approximately is "near future" ?