Skip to content
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

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

Open
tommywo opened this issue Jun 17, 2019 · 7 comments

Comments

@tommywo
Copy link
Contributor

tommywo commented Jun 17, 2019

ERROR Error consuming line XML configurations will be removed in the next release.  Convert cflint-config.xml to json.
@sanjeevaReddych
Copy link

is this issue fixed?

@jeffruel
Copy link

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

@indcsarl
Copy link

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

@mrhcon
Copy link

mrhcon commented Apr 17, 2024

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
Copy link

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

@mrhcon
Copy link

mrhcon commented Apr 17, 2024

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
Copy link

@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 !

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

No branches or pull requests

5 participants