Merge branch 'eclipse-cdt:main' into SyncLRUAccess

Author: ramele1907

.gitattributes

@@ -48,7 +48,6 @@ Dockerfile text
 *.yaml text
 *.yml text
 .dockerignore text
-uid_entrypoint text
 
 # Qt
 *.pro text
@@ -157,6 +156,15 @@ output-1 text
 *.srec text eol=lf
 test_commands text
 
+# Font awesome files (other files could have the same extensions)
+*.eot binary
+*.less binary
+*.otf binary
+*.scss binary
+*.ttf binary
+*.woff binary
+*.woff2 binary
+
 # Other special files
 cdtOptions text
 .clang-format text

.github/workflows/build-test.yml

@@ -5,32 +5,40 @@ on: [push, pull_request]
 jobs:
   build:
 
-    runs-on: ubuntu-20.04
-    timeout-minutes: 90
+    runs-on: ubuntu-24.04
+    timeout-minutes: 120
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
       with:
         fetch-depth: 0
-    - uses: dorny/paths-filter@v2
+    - uses: dorny/paths-filter@v3
       id: filter
       with:
+        # dsf filters are to know when to run dsf-gdb tests (See ref below)
+        # it includes any changes to debug, or anything likely to affect gdb
+        # testing
         filters: |
           dsf:
             - 'dsf-gdb/**'
             - 'dsf/**'
             - 'debug/**'
             - 'jtag/**'
+            - 'pom.xml'
+            - 'releng/**'
+            - '.github/**'
+          docs:
+            - 'doc/org.eclipse.cdt.doc.user/**'
     - name: Set up JDK 21
-      uses: actions/setup-java@v3
+      uses: actions/setup-java@v4
       with:
         java-version: '21'
         distribution: 'temurin'
         cache: maven
     - name: Set up Maven
-      uses: stCarolas/setup-maven@07fbbe97d97ef44336b7382563d66743297e442f # v4.5
+      uses: stCarolas/setup-maven@v5
       with:
-        maven-version: 3.9.2
+        maven-version: 3.9.6
     - name: Install GCC & GDB & other build essentials
       run: |
         sudo apt-get update
@@ -49,18 +57,38 @@ jobs:
           -DexcludedGroups=flakyTest,slowTest \
           -Ddsf.gdb.tests.timeout.multiplier=50 \
           -Ddsf-gdb.skip.tests=$(test ${{ steps.filter.outputs.dsf }} == 'false' && echo 'true' || echo 'false') \
-          -Dindexer.timeout=300
+          -Dindexer.timeout=300 \
+          -Dsurefire.rerunFailingTestsCount=3
     - name: Upload Logs
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       if: success() || failure()
       with:
-        name: Code Cleanliness Detailed Logs
-        path: '*.log'
+        name: Detailed Logs
+        path: '**/*.log'
+    - name: Prepare Test Results for upload
+      if: (success() || failure())
+      run: |
+        cp ${{ github.event_path }} event.json
     - name: Upload Test Results
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       if: success() || failure()
       with:
         name: test-results
         path: |
+          event.json
           */*/target/surefire-reports/*.xml
           terminal/plugins/org.eclipse.tm.terminal.test/target/surefire-reports/*.xml
+    - name: Prepare Docs for upload
+      if: (success() || failure()) && steps.filter.outputs.docs
+      run: |
+        mkdir -p docs/user
+        cd docs/user
+        unzip ../../releng/org.eclipse.cdt.repo/target/repository/plugins/org.eclipse.cdt.doc.user_*.jar
+    - name: Upload Docs
+      uses: actions/upload-artifact@v4
+      if: (success() || failure()) && steps.filter.outputs.docs
+      with:
+        name: docs
+        include-hidden-files: true
+        path: |
+          docs/**

.github/workflows/code-cleanliness.yml

@@ -7,22 +7,22 @@ jobs:
     runs-on: ubuntu-20.04
 
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Run Check Code Cleanliness with Docker
         uses: addnab/docker-run-action@v3
         with:
-          image: quay.io/eclipse-cdt/cdt-infra-plus-eclipse-install-github@sha256:6949adee26f78e9968e16d52bc3accfd7b51d0f16c473ad4b6f1caee849ab519
+          image: quay.io/eclipse-cdt/cdt-infra-github@sha256:3d745b7b84e3f9f9492cc1d280ea3b44028a92c7e9748d1ea8771fed211b5dc4
           options: -v ${{ github.workspace }}:/work
           run: |
-            set -x
+            set -ex
             cd /work
             ./releng/scripts/check_code_cleanliness_only.sh
             ./releng/scripts/check_bundle_versions.sh
             ./releng/scripts/check_bundle_versions_report.sh
       - name: Upload Logs
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         if: success() || failure()
         with:
           name: Code Cleanliness Detailed Logs

.github/workflows/licensecheck.yml

@@ -1,6 +1,6 @@
 # This workflow will check for Maven projects if the licenses of all (transitive) dependencies are vetted.
 
-name: License vetting status check
+name: License check
 
 on:
   push:
@@ -13,8 +13,8 @@ on:
     types: [created]
 
 jobs:
-  call-license-check:
-    uses: eclipse/dash-licenses/.github/workflows/mavenLicenseCheck.yml@master
+  call:
+    uses: eclipse-dash/dash-licenses/.github/workflows/mavenLicenseCheck.yml@master
     with:
       projectId: tools.cdt
     secrets:

.github/workflows/report.yml

@@ -14,7 +14,7 @@ jobs:
 
     steps:
       - name: Download Test Report
-        uses: dawidd6/action-download-artifact@v2
+        uses: dawidd6/action-download-artifact@v7
         with:
           name: test-results
           path: test-results
@@ -26,3 +26,5 @@ jobs:
         with:
           commit: ${{ github.event.workflow_run.head_sha }}
           junit_files: "test-results/**/*.xml"
+          event_file: test-results/event.json
+          event_name: ${{ github.event.workflow_run.event }}

.mvn/extensions.xml

@@ -3,6 +3,6 @@
   <extension>
     <groupId>org.eclipse.tycho</groupId>
     <artifactId>tycho-build</artifactId>
-    <version>4.0.6</version>
+    <version>4.0.10</version>
   </extension>
 </extensions>

BUILDING.md

@@ -25,7 +25,7 @@ To build CDT plug-ins you need a standard Maven & Java development environment.
 The CI build automatically run code cleanliness checks. To run them on your computer it is recommended to use the Docker image, for example like this from the root of the checked out CDT repo:
 
 ```sh
-docker run --rm -it -v $(git rev-parse --show-toplevel):/work -w /work/$(git rev-parse --show-prefix) --cap-add=SYS_PTRACE --security-opt seccomp=unconfined quay.io/eclipse-cdt/cdt-infra-plus-eclipse-install:latest releng/scripts/check_code_cleanliness.sh
+docker run --rm -it -v $(git rev-parse --show-toplevel):/work -w /work/$(git rev-parse --show-prefix) --cap-add=SYS_PTRACE --security-opt seccomp=unconfined quay.io/eclipse-cdt/cdt-infra:latest releng/scripts/check_code_cleanliness.sh
 ```
 
 ### Profiles
@@ -160,7 +160,7 @@ An additional tip is to set the following in `.gitconfig` to allow you to diff `
 
 When the host is Windows, getting docker to behave as encoded in the pom.xml may be challenging, instead a command like this will probably work (replace your path to git root). Note that running this in git bash causes problems because of the /work in the command line arguments. (TODO integrate this command line way of running into the pom.xml so the original instructions work.)
 
-`docker 'run' '--rm' '-t' '-v' 'D:\cdt\git\org.eclipse.cdt:/work' '-w' '/work/core/org.eclipse.cdt.core.native' 'quay.io/eclipse-cdt/cdt-infra-eclipse-full:latest' 'make' '-C' 'native_src' 'rebuild'`
+`docker 'run' '--rm' '-t' '-v' 'D:\cdt\git\org.eclipse.cdt:/work' '-w' '/work/core/org.eclipse.cdt.core.native' 'quay.io/eclipse-cdt/cdt-infra:latest' 'make' '-C' 'native_src' 'rebuild'`
 
 See also `jniheaders` profile above.
 

Jenkinsfile

@@ -6,6 +6,7 @@ pipeline {
   }
   options {
     timestamps()
+    buildDiscarder(logRotator(numToKeepStr: '10', artifactNumToKeepStr: '2'))
   }
   stages {
     stage('initialize PGP') {
@@ -53,6 +54,12 @@ pipeline {
                       -Dmaven.repo.local=/home/jenkins/.m2/repository \
                       --settings /home/jenkins/.m2/settings.xml \
                       '''
+                sh '''
+                  echo "TIMESTAMP: $(date)" > releng/org.eclipse.cdt.repo/target/repository/ci-and-git-info.txt
+                  echo "CI URL: ${BUILD_URL}" >> releng/org.eclipse.cdt.repo/target/repository/ci-and-git-info.txt
+                  echo "Most recent git commits: (output of  git log --graph --pretty='tformat:%h [%ci] - %s' -20)"  >> releng/org.eclipse.cdt.repo/target/repository/ci-and-git-info.txt
+                  git log --graph --pretty='tformat:%h [%ci] - %s' -20 | tee -a releng/org.eclipse.cdt.repo/target/repository/ci-and-git-info.txt
+                '''
               }
             }
           }

NewAndNoteworthy/CDT-12.0.md

@@ -6,8 +6,44 @@ This is the New & Noteworthy page for CDT 12.0 which is part of Eclipse 2025-03
 
 # Release Notes
 
+## Minimum version of GLIBC required
+
+The minimum version of GLIBC required is now 2.31.
+This version can be found in Ubuntu 20.04 and later, RHEL 9.0 and later and other distros as well.
+CDT's native components will likely work with older versions of glibc too, assuming they provide the required APIs for Eclipse CDT.
+
+# Core Build
+
+## More CMake build settings are now available in the user interface
+
+The CMake build setting GUI has been updated to include more CMake settings, and some of the settings that did not used to do the correct thing have been updated for more consistent behavior.
+The way these settings are saved has been slightly modified, meaning workspaces with CMake projects from before CDT 12 will have their build settings restored to defaults.
+Build settings can be customized by unchecking "Use default CMake settings".
+
+TODO: Before release add the final screenshot for the build settings here. I am not including it now because the UI keeps changing.
+
+## Default build system generator for CMake changed to Ninja on all platforms
+
+The default for CMake's  build system generator is now Ninja on all platforms.
+Users who want to use other build system generators can select their desired generator in the build settings.
+
 # Managed Build
 
+## New *C Project* and new *C++ Project* available via *New C/C++ Project* wizard
+
+The separate new C and C++ project wizards are now exclusively available via the *New C/C++ Project* wizard.
+From the second page of *New C/C++ Project* wizard select *C Managed Build* to access the *New C Project* wizard and select *C++ Managed Build* to access the *New C++ Project* wizard.
+
+See [Issue #965](https://github.com/eclipse-cdt/cdt/issues/965) for additional details, including how to restore these menu entries if your Eclipse CDT product depends on it.
+
+## New *Makefile Project with Existing Code* available via *Existing Code as Makefile Project* import wizard
+
+The *Makefile Project with Existing Code* wizard is no longer available in the new project wizard.
+For users who need it, it remains available in the *Existing Code as Makefile Project* import wizard.
+Most users should be using the *Makefile project* type in the *New C/C++ Project* wizard.
+
+See [Issue #965](https://github.com/eclipse-cdt/cdt/issues/965) for additional details, including how to restore these menu entries if your Eclipse CDT product depends on it.
+
 ## Other objects for GNU archive files
 
 The managed build system now provides an option to specify other object files to be included when building GNU archive files:
@@ -16,8 +52,40 @@ The managed build system now provides an option to specify other object files to
 
 The new option applies to static library projects using a _Cross GCC_, _Cygwin GCC_, _Linux GCC_ or _MinGW GCC_ toolchain.
 
+# Debug
+
+## DSF Preference Pages always visible
+
+The DSF Preference pages (Preferences -> C/C++ -> Debug -> GDB and children) are not always shown to users.
+Prior to CDT 12 these were not visible until after the first debug session was started.
+
+At the first debug session CDT enables the [activity](https://help.eclipse.org/latest/topic/org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_activities.html) for DSF (`org.eclipse.cdt.debug.dsfgdbActivity`), with this change nothing in CDT is bound to this activity key anymore.
+
+## Preferences -> Run/Debug -> View Performance relocated
+
+The View Performance preference page, which is CDT specific, has been relocated to the Preferences -> C/C++ -> Debug section of preferences.
+This only affects where in the Preferences tree the page is located, the preferences and key names have not changed.
+In addition, this page is always visible.
+
+# Terminal
+
+## Default encoding for terminal is now UTF-8
+
+For a [while](https://eclipse.dev/eclipse/news/4.24/platform.html#explicit-encoding-workspaces), the default encoding in Eclipse has been UTF-8.
+Starting in CDT 12, the Terminal will now default to UTF-8.
+
+<p align="center"><img src="images/CDT-12.0-default-terminal-encoding.png"></p>
+
 # API Changes, current and planned
 
+## CMake Support easier for extenders and ISVs
+
+Improvements to the API for CMake has made it easier to extend and specialize CMake for ISVs.
+A fully worked example demonstrating the support is now provided in the CDT source in [org.eclipse.cdt.cmake.example](https://github.com/eclipse-cdt/cdt/tree/main/cmake/org.eclipse.cdt.cmake.example).
+This example demonstrates the API, and how to contribute a new project wizard to make such a project.
+
+<p align="center"><img src="images/CDT-12.0-cmake-example-project-for-isvs.png"></p>
+
 ## Breaking API changes
 
 Please see [CHANGELOG-API](CHANGELOG-API.md) for details on the breaking API changes in this release as well as future planned API changes.
@@ -26,6 +94,14 @@ Please see [CHANGELOG-API](CHANGELOG-API.md) for details on the breaking API cha
 
 See [Noteworthy issues and PRs](https://github.com/eclipse-cdt/cdt/issues?q=is%3Aclosed+label%3Anoteworthy+milestone%3A12.0.0) for this release in the issue/PR tracker.
 
+## Improved launch configuration for CMake and other Core Build System projects
+
+The CMake and CBS Makefile project launch configurations for local applications have an improved Main tab and new Arguments, Environment, Debugger, Source, and Common tabs.
+
 # Bugs Fixed in this Release
 
-See [GitHub milestones](https://github.com/eclipse-cdt/cdt/milestone/11?closed=1)
+See GitHub milestones:
+- [![12.0.0 M1](https://img.shields.io/github/milestones/issues-total/eclipse-cdt/cdt/12)](https://github.com/eclipse-cdt/cdt/milestone/12?closed=1)
+- [![12.0.0 M2](https://img.shields.io/github/milestones/issues-total/eclipse-cdt/cdt/13)](https://github.com/eclipse-cdt/cdt/milestone/13?closed=1)
+- [![12.0.0 M3](https://img.shields.io/github/milestones/issues-total/eclipse-cdt/cdt/18)](https://github.com/eclipse-cdt/cdt/milestone/18?closed=1)
+- [![12.0.0](https://img.shields.io/github/milestones/issues-total/eclipse-cdt/cdt/14)](https://github.com/eclipse-cdt/cdt/milestone/14?closed=1)

NewAndNoteworthy/CHANGELOG-API.md

@@ -8,6 +8,23 @@ This section describes API removals that occurred in past releases, and upcoming
 
 Below is the detailed descriptions of API changes and mitigation efforts API consumers need to take.
 
+## API Changes in CDT 12.0.
+
+### org.eclipse.cdt.cmake.core.properties refactored
+
+A significant simplification to the CMake build properties was completed, this included removing some API that was not used.
+The following classes have been removed or modified in API breaking ways:
+
+- org.eclipse.cdt.cmake.core.properties.ICMakePropertiesController removed
+- org.eclipse.cdt.cmake.core.properties.IGeneralProperties removed
+- org.eclipse.cdt.cmake.core.properties.IOsOverrides removed
+- org.eclipse.cdt.cmake.core.properties.ICMakeProperties:
+  - new methods added to compensate for removal of IOsOverrides
+  - reset method removed
+  - spelling corrected for methods with Uninitialized in the name
+  - setWarnUnused renamed to setWarnUnusedVars and isWarnUnused renamed to isWarnUnusedVars
+
+
 ## API Changes in CDT 11.5.
 
 ### org.eclipse.cdt.make.ui.dialogs.DiscoveredPathContainerPage removed

NewAndNoteworthy/README.md

@@ -2,7 +2,7 @@
 
 What's new and noteworthy in:
 
-- [CDT 12.0/2024-09](CDT-12.0.md)
+- [CDT 12.0/2025-03](CDT-12.0.md)
 - [CDT 11.6/2024-06](CDT-11.6.md)
 - [CDT 11.5/2024-03](CDT-11.5.md)
 - [CDT 11.4/2023-12](CDT-11.4.md)

NewAndNoteworthy/images/CDT-12.0-cmake-example-project-for-isvs.png

@@ -69,6 +69,7 @@ There are many third-party addons for CDT to make it more productive.
 * [CDT LSP](https://github.com/eclipse-cdt/cdt-lsp#readme): LSP based C/C++ Editor provided by the Eclipse CDT project
 * [cmake4eclipse](https://github.com/15knots/cmake4eclipse#abstract): This Eclipse plug-in automatically generates build-scripts for the Eclipse CDT managed build system from CMake scripts.
 * [Sloeber](http://eclipse.baeyens.it/): Eclipse Plugins based on Arduino toolchains or a enhanced Arduino IDE.
+* [SonarQube for Eclipse](https://marketplace.eclipse.org/content/sonarqube-ide): Eclipse plug-in for static analysis for quality and security issues in your C/C++ code directly inside the IDE.
 * [CUTE](https://cute-test.com/): C++ unit testing plug-in
 * [Bracketeer](https://marketplace.eclipse.org/content/bracketeer-cc-cdt): Auto-comments on closing brackets and highlight of matching/mismatching brackets
 * And many more in the [Eclipse Marketplace](https://marketplace.eclipse.org/), for example, try the [CDT tag](https://marketplace.eclipse.org/category/free-tagging/cdt)

NewAndNoteworthy/images/CDT-12.0-default-terminal-encoding.png

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %Bundle-Name.0
 Bundle-SymbolicName: org.eclipse.cdt.autotools.core;singleton:=true
-Bundle-Version: 2.2.300.qualifier
+Bundle-Version: 2.2.400.qualifier
 Bundle-Activator: org.eclipse.cdt.autotools.core.AutotoolsPlugin
 Bundle-Localization: plugin
 Require-Bundle: org.eclipse.ui;bundle-version="3.4.0",

README.md

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %Bundle-Name.0
 Bundle-SymbolicName: org.eclipse.cdt.autotools.ui;singleton:=true
-Bundle-Version: 2.2.400.qualifier
+Bundle-Version: 2.2.500.qualifier
 Bundle-Activator: org.eclipse.cdt.autotools.ui.AutotoolsUIPlugin
 Bundle-Localization: plugin
 Bundle-Vendor: %provider