[
https://issues.apache.org/jira/browse/DAFFODIL-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2856.
-----------------------------------
Verified the specified commit (commit e2a1835b7d23057f4916ae50b8d08b605ecf714e)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Verified the .github/workflows/main.yml file now specifies/uses
SonarSource/[email protected].
Verified on https://github.com/apache/daffodil/commits/main/ that the
SonarCloud Scan passes on this and subsequent commits with the details
correctly specifying Java 17 was used.
> Configure SonarCloud scan run on Java 17
> ----------------------------------------
>
> Key: DAFFODIL-2856
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2856
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Assignee: Peter Katlic
> Priority: Critical
> Fix For: 3.7.0
>
>
> Received an email with the following from SonarCloud:
> {quote}
> Starting from the 15th of November 2023, SonarCloud will no longer accept
> scans executed using Java 11. This decision has been made to ensure the
> platform's compatibility with the latest technologies and to provide you with
> an enhanced experience.
> To continue benefiting from SonarCloud's advanced features and analysis
> capabilities, we strongly encourage you to migrate your runtime environment
> for the analysis to Java 17 as soon as possible.{quote}
> We should update our github action to run on our Java 17 matrix instead of
> Java 11:
> https://github.com/apache/daffodil/blob/main/.github/workflows/main.yml#L88-L95
> Marking as critical since this will happen fairly soon, and we don't want
> builds to start breaking.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
