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

Move Sonar to JDK17 build #2561

Closed
smcvb opened this issue Jan 16, 2023 · 0 comments · Fixed by #2574
Closed

Move Sonar to JDK17 build #2561

smcvb opened this issue Jan 16, 2023 · 0 comments · Fixed by #2574
Assignees
Labels
Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Milestone

Comments

@smcvb
Copy link
Member

smcvb commented Jan 16, 2023

Enhancement Description

Since the JDK17 build now works as intended, we can move the Sonar integration to JDK17.
This has the additional benefit that we can include the Spring Boot 3 tests #2534 to the coverage report, ensuring we don't miss anything.

Current Behaviour

The Sonar integration uses JDK11 for Axon Framework.

Wanted Behaviour

The Sonar integration uses JDK17 for Axon Framework. Plus, we include the Spring Boot 3 tests from #2534.

@smcvb smcvb added Type: Enhancement Use to signal an issue enhances an already existing feature of the project. Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. labels Jan 16, 2023
@smcvb smcvb added this to the Release 4.8.0 milestone Jan 16, 2023
@gklijs gklijs self-assigned this Jan 23, 2023
@smcvb smcvb added the Status: In Progress Use to signal this issue is actively worked on. label Jan 23, 2023
@smcvb smcvb modified the milestones: Release 4.8.0, Release 4.7.0 Jan 23, 2023
smcvb added a commit that referenced this issue Jan 23, 2023
@smcvb smcvb added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants