search

stepstone-tech / sonar-coldfusion

SonarQube ColdFusion Analyzer
Apache License 2.0
24 stars 18 forks source link

ERROR Error consuming line XML configurations will be removed in the next release. Convert cflint-config.xml to json. #24

Open tommywo opened 5 years ago

tommywo commented 5 years ago 
ERROR Error consuming line XML configurations will be removed in the next release.  Convert cflint-config.xml to json.
sanjeevaReddych commented 2 years ago

is this issue fixed?

jeffruel commented 9 months ago

We have the exact same error. We are using SonarQube 9.9.2. Have you ever found a solution for this error ?

indcsarl commented 8 months ago

We have the exact same error. We are using SonarQube 10.3. it would be great to be able to use this :-)

mrhcon commented 5 months ago

This is a old post, but I did find a way to fix the issue in sonarQube v10.5 Log into the sonarQube web interface. Go to Administration in the top navigation bar. In General Settings, select ColdFusion in the left navigation bar. In the Java executable options field add the following: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED. Select the Save button.

jeffruel commented 5 months ago

@mrhcon Thanks for sharing this ! We still use version 9.9.2, bit it's something worth a try in our lab environment.

mrhcon commented 5 months ago

The ultimate issue is that the plugin is java v8 and sonarQube is java v17. Starting from Java 9, the introduction of the Java Platform Module System (JPMS) added more granularity to the visibility and accessibility of classes and members. This system is designed to encapsulate Java's internal APIs and prevent unintended usage, which can lead to more robust and secure applications. However, this also means that some techniques that worked in Java 8 and earlier might encounter access restrictions in Java 9 and later versions. What I proposed was ONLY a workaround not permanent solution.

jeffruel commented 5 months ago

@mrhcon We tried it and even if the error is still present in the pipeline task, the analysis completes and we get results. It is indeed a workaround, but it helps us. Thanks again !