-
Notifications
You must be signed in to change notification settings - Fork 50
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 10.x (Java 17 compatible) #243
SonarQube 10.x (Java 17 compatible) #243
Conversation
de82537
to
a6bf08b
Compare
Hi, Thank you so much for looking into this |
Hi Max,
I'm happy to help. The migration is complete and functioning as expected. You can check out the branch and build the plugin package with the existing code. The release depends on Principal Technical Lead Tomasz Niedzwiedz's review and his ideas for future improvements. He is at the AdaptTo conference until Thursday, so the official release will likely be next week. I will confirm the exact release date and let you know.
[VML Logo]
Tomasz Strzelecki
Software Engineer
T +48 61 843 30 41
From: Max K. ***@***.***>
Date: Tuesday, 22 October 2024 at 10:01
To: wttech/AEM-Rules-for-SonarQube ***@***.***>
Cc: Tomasz Strzelecki ***@***.***>, Author ***@***.***>
Subject: Re: [wttech/AEM-Rules-for-SonarQube] 10.x version migration (PR #243)
External:
Hi,
So glad you are working on this. We deactivated the plugin so far as it kept us from building our releases after upgrading to SonarQube 10.X. Can you give a rough estimate when this migration will be available just for planning purposes.
Thank you so much for looking into this
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/wttech/AEM-Rules-for-SonarQube/pull/243*issuecomment-2428541565__;Iw!!IfJP2Nwhk5Z0yJ43lA!Pde9rC0aBOaqe0mwGqIAvrnBH4-srq6pIxcVNTIZXA7N2S3rwSsl5bwiWvzIyOPuHZvIEimvd3XyEohhiHCgggcmEY8PpBGBWya9gI_b$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYFA6T3OJWEV2Q4DAG5BLRTZ4YA4NAVCNFSM6AAAAABQFRMPUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGU2DCNJWGU__;!!IfJP2Nwhk5Z0yJ43lA!Pde9rC0aBOaqe0mwGqIAvrnBH4-srq6pIxcVNTIZXA7N2S3rwSsl5bwiWvzIyOPuHZvIEimvd3XyEohhiHCgggcmEY8PpBGBW7YYrXT5$>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
f643594
to
1966e63
Compare
f164a83
to
6eec6ab
Compare
@macskay, I would be extremely grateful for your feedback on the 1.7 plugin version. I'd like to release it as the latest version. You can find it here: https://github.com/wttech/AEM-Rules-for-SonarQube/releases/tag/v1.7 |
Awesome, I was out of order with COVID the past couple of days. Will test it out and get backj to you as soon as I have news :) |
Unfortunately it did not work for us. We tried installing but the SonarQube Server restarts after throwing the following error:
We are on a 10.7 installation. After removing the plugin again SonarQube starts without a problem. |
Ok. Thank you for your feedback. I will try to reproduce the issue and come back to you. I tried to use plugin with 10.7 instance, but I worked with clean installation without any data. In that case it worked without issues. It might be the case that new version doesn't support backward compatibility with ES indexes. |
any news on this @tomasz-strzelecki-vml ? |
@macskay can you share the exact version of SonarQube server which you use? |
@macskay I tried to reproduce the issue locally but I can't. I recommend to rebuild ES indices. On 10.7-community image they are located in path
SonarQube will recreate indices on startup and plugin should work without issues. |
@macskay any news? |
I will try that, even though I think I have. We are on SonnarQube 10.7. Will get back to you as soon as I tried out purging the es indicies. |
No description provided.