Changes

Use stable URL for Platform 4.28 dependency

Part of #420

recognize source file extensions ".ccm", ".cxxm", and ".c++m" (#422)

* recognize source file extensions ".ccm", ".cxxm", and ".c++m"

cmake 3.27 release notes: The "CXX" language now treats source file
extensions ".ccm", ".cxxm", and ".c++m" as C++.

Signed-off-by: 15knots <11367029+15knots@users.noreply.github.com>

Eliminate memory leak in Default Binary File Editor

Lock snakeyaml to expected 1.x version

Snakeyml recentlyish came out with 2.0 version and more recently
TM4E started using the 2.0 version. As TM4E snapshots are in our
target platform we started failing as we started wiring to the newer
version due to a missing underbound on our dependency.

A separate task of updating to recent snakeyaml will be done as part
of #387

Propagate exceptions in default binary file viewer

Postpone build container creation to build start. Fixes possible Eclipse freeze. (#433)

The creation of the build container for Core Build projects is
postponed to the start of the build process.

StandardBuildConfiguration getBuildContainer and setBuildContainer
have been cleaned up.

CBuildConfiguration creation is started via
CBuildConfigurationManager.getBuildConfiguration(IBuildConfiguration)
which holds a lock on the HashMap 'configs'. Creation of
StandardBuildConfiguration triggered, via applyProperties and
getBuildContainer(), a Folder.create which loops back to
CBuildConfigurationManager.getBuildConfiguration().
For detailed traces see https://github.com/eclipse-cdt/cdt/issues/424

Fixes #424

Support DWARF attribute form DW_FORM_implicit_const

Support DWARF v5 content form data

[#449] Import memory window is not working as expected

Use `SWT.OPEN` style for import dialogs

Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>

[#449] Import memory window is not working as expected

Increment version for org.eclipse.cdt.debug.ui.memory.transport

Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>

Format target file

The target file has been formatted with the formatter
in the Target editor when in the Source tab (Context menu ->
Source -> Format).

Move all dependencies to maven direct where possible

Includes:

- Sign all artifacts, particularly 3rd party with CDT's PGP key
- Using maven version managed and updated by EF Webmasters
- Update to latest SnakeYAML
- Move some 3rd party dependencies to Import-Package (instead of
  Require-Bundle)

Prepare repo for CDT 11.3.0 development

Some bundles are bumped because dev happened between 11.2 release and
this version bump. The most significant change that happened
was the bump in Tycho version which changed ECJ version and
hence some class files changed

Part of #420

Update to latest version of deps

Using https://github.com/eclipse-orbit/orbit-simrel/blob/main/report/maven-osgi/cdt/REPORT.md

Part of #420

Fix Variables button for Working Directory in launch config

Fixes #463

Use last released LinuxTools docker

At the moment there are some resolution issues on the nightly
versions of LinuxTools docker components, so for now use the
latest release rather than nightly.

See https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/issues/232

Update target platform to latest Eclipse Platform milestone

This includes updating to 3rd party dependencies coming from Maven
so that everything resolves properly. In particular spifly
required asm, and by doing `includeDependencyDepth="direct"` that
dependency is included in the target platform.

Explicitly include ASM in our target platform

My last attempt at this in 4aa51673ab I had set
includeDependencyDepth="direct" but that pulled in a bunch
of unintended dependencies. Instead explicitly add the ASM
dependency.

Move back to Linux Tools Docker nightly

The commit resolves the resolution error that was raised in
https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/issues/232

I have raised an issue in PDE here:
https://github.com/eclipse-pde/eclipse.pde/issues/675

Make GitHub issue template more relevant (#468)

The old template was the default for GitHub, but it was off the mark
a little for some aspects. This change hopes to make the template
more useful

Eliminate GC resource leak

Move entirely from the old Orbit repos to the new aggregated ones (#486)

I have also removed the now unused dependencies.

[#484] Add extension point for custom icons of C/C++ source files (#485)

* [#484] Add extension point for custom icons of C/C++ source files

fixes #484

Fix version dependency on o.e.c.managedbuilder.core

Resolve cast exception - fixup for inferring generic types (#490)

Long ago in 334702ee05048a95e131530ddb80fbf2654dfef5 generic types
were added. However in at least one place a previous assumption
that existed was broken. That assumption was the true
type of ResourceInfo.getTools() would be Tool[] as opposed to ITool[].
That commit broke it for ResourceConfiguration.getTools()

Internally in CDT ITool is in practice always Tool, and as a result
there are lots of downcast from ITool -> Tool. However ITool[] cannot
be downcast to Tool[] unless the original type was Tool[].

Instead we use Arrays.copyOf to copy the array into the correct
array type.

Steps to reproduce the problem now fixed:

1. Create a Managed Build executable project.
2. Open the properties window of the source file (as opposed to project)
3. At the Properties page, navigate to "C/C++ Build/Tool Chain Editor".
4. Click the "Apply" button.

Add NXP LinkServer definitions

Add unique display name for some test plug-ins

Clean up target platform

Until https://github.com/eclipse-cdt/cdt/pull/495 can be resolved
fully, apply some of the required changes.

- wildwebdeveloper was out of date, however we don't really
  need wwd in CDT, but some of our dependencies have requirements
  that are fufilled (e.g. linuxtools)
- duplicate entry for hamcrest 2.2 removed (other entry was just
  above it!)

Fix test cases that recently regressed

Recently new extensions were added to CDT for C++ modules in #422
At the time some test failures were not noticed. This change patches
those failing tests.

Fixes #454

Remove and ignore object references from Yaml files

Yaml 2.0 fixes CVE-2022–1471 to error on object references. This
commit adapts our use of Yaml to not output object references
anymore and on loading explicitly allow object references to
expected types.

Fixes #498

Explicitly activate shell for launchbar selector

In https://github.com/eclipse-platform/eclipse.platform.swt/issues/450
the behaviour was changed so that setFocus no longer activates the shell
by default. Therefore when creating the popup shell and setting the focus
the overall focus was still on a control in the main eclipse shell.

This affected Eclipse SWT/Platform 4.29 M1 and has been changed for
M3. However there is intention to (possibly) change the default back
to not activating in setFocus. If that happens this patch will be ready
for it, and in the meantime (until CDT changes to M3) it resolves this
test failure:

`createNewLaunchConfig (org.eclipse.launchbar.ui.tests.internal.CreateLaunchConfigTests) with error`

full trace:

```java
org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Create Launch Configuration'
	at org.eclipse.launchbar.ui.tests.internal.CreateLaunchConfigTests.createNewLaunchConfig(CreateLaunchConfigTests.java:77)
Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 10000 ms.: Could not find shell matching: with text 'Create Launch Configuration'
	at org.eclipse.launchbar.ui.tests.internal.CreateLaunchConfigTests.createNewLaunchConfig(CreateLaunchConfigTests.java:77)
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
```

Fix meson build under Docker Tooling (#491)

* Fix meson build under Docker Tooling

- add new IToolChainConstants containing SECCOMP_UNCONFINED property constant
- add new setLauncher() method to CBuildConfiguration so that
  watchProcess() can be used for container building
- enhance ContainerCommandLauncher to discover specification of
  SECCOMP_UNDEFINED boolean option for execute() so "seccomp=undefined" can be specified
- fix ContainerCommandLauncherFactory.verifyIncludePaths() to only
  look at filtered includes that have been made absolute and to
  recognize matches when the prefix shows up in the loaded list
- add setting a property to ContainerGCCToolChain to set SECCOMP_UNCONFINED to true
  by default for the time-being
- when generating scannerinfo, specify "seccomp=unconfined"
- in ContainerGCCToolChain.startBuildProcess() remove extraneous
  banner statement and ensure that the build directory is created
- fixes #479

Fix NPE when language entry is incomplete (as it is for LLVM)

Fixup some API version errors

Follow up for #491

Update target platform for 2023-09 M3 Orbit updates

Includes an I-build of platform that needs to updated to M3
platform when it is released on Friday

Fixes #509

Refactor XML file handling

Split check code cleanliness into two build steps

A while ago we made the "Make sure all versions have been bumped
appropriately compared to the baseline" output to another file
to make it clearer. This refactor splits it up into different
build steps instead so that I don't have to open an additional
log file.

Update to Tycho 4.0.1

The error handling in Tycho 4 identifies when bundles are listed
in category.xml but not available. The removed bundles were
not in the output, and with this change the error is resolved
in the build.

Updated setting for maven enforcer to match Tycho requirements.

Add API Baseline checking to the build

Stop checking baseline-compare-and-replace in build and test workflow

This is checked in the code cleanliness workflow and by failing the
main build here causes the tests not to run and the tests are more
important. Similar to the new api-baseline-check that doesn't
run in the main workflow

Fix the check bundle versions check

Use latest build of CDT, rather than latest release in target platform

Update to platform 2023-09 M3 contribution

Remove assumption that strings are always intern

The pre-existing code assumed that string (qName) passed in
to start and end element was always interned and compared
those strings to constants using ==. Instead rewrite
code using switch statements on the strings.

Also includes small change to the exception handling so that
code analysis can correctly where exceptions are always thrown.
i.e. instead of hiding a throw in an always throwing method,
return the exception and throw it at the call site.

Trim excess whitespace in Boost test output

The code for boost test running parsing left
all the excess whitespace from the XML file.
This led to a lot whitespace in messages
in the UI. This change trims leading and
trailing whitespace, but preserves whitespace
within a message.

Support Context tags in Boost test runs

Boost a while ago added Context tags, this commit makes
those context tags supported in the testsrunner code of CDT

See also https://www.boost.org/doc/libs/1_82_0/libs/test/doc/html/boost_test/test_output/test_tools_support_for_logging/contexts.html

Fixes 459

allow github to index the build directory

https://docs.github.com/en/search-github/searching-on-github/finding-files-on-github

Improve memory search results page

The Memory Browser and Memory views will jump to the memory
address after a user selects a value from the Memory Search
Result list. If the views belong to the same tab group as
the Search view, then it might not be very intuitive for
the user to switch back to one of the Memory views and see
the effect of the selection.

The current commit adds on the the double click listener
(from MemorySearchResultsPage.java) the behavior to refocus
on the Memory Browser/ Memory view.

Resolves: #515

Code cleanup on Memory Search Result Page

- Use modern java instanceof
- Log unexpected exceptions
- reorder tests
- add missing null checks
- invert some if conditions for less nesting

 Add ability to prevent terminal title updates from ANSI Escape sequence

When a more complete implementation of ANSI Escape sequence for
renaming terminal titles was added in
[CDT 10.2](https://github.com/eclipse-cdt/cdt/blob/main/NewAndNoteworthy/CDT-10.2.md#rename-terminal-tab)
it caused a regression in use cases where extenders of the terminal
wanted to retain control of the terminal's title.

This commit adds a new flag that will prevent the title of the
terminal tab from being updated from ANSI escape sequences.

Fixes #494

Disable running tests on Jenkins

The Jenkins CI at EF is running very slowly recently and all
tests are timing out. The tests work fine locally and find
on GitHub actions runners.

Therefore on the Jenkins CI build without running the tests.

Run only the code cleanliness on Jenkins CI

I recently split code cleanliness into two parts, and since in Jenkins
the baseline-compare-and-replace and api-baseline-check run on the main
build we don't need to run them on the cleanliness pass too. Therefore
run the "only" script in the code formatting checks stage to speed up
build and avoid duplicated work.

Print the memory allocated to maven on Jenkins and increase the memory available.

Use new simrel-orbit p2 repo in Oomph setup

Fixes #511

Add support for ESC[#X to VT100

This escape sequence can be generated when using Powershell on
Windows (and possibly other places too) to erase number of
characters.

Change-Id: I32405f51a3f91fd8653d44f2676a5c85b696ef99

Allocate much more ram to the Pod on Jenkins

I think with some of the recent changes (Tycho 4, API baselines,
maybe even new dependency on Platform M3) it may be that our memory
requirements have gone up substantially for the build.

Also, with Sonar in the works that also requires more memory.

Therefore see if the EF's JIPP infra will allocate 10G of ram to
our build.

This should fix all the "Killed" messages randomly in the CDT builds.
https://wiki.eclipse.org/Jenkins#What_is_killing_my_build.3F_I.27m_using_custom_containers.21

Revert "Disable running tests on Jenkins"

With the extra memory in the parent commit the build is succeeding again
and therefore we don't need tests disabled anymore.

This reverts commit bee7e0db0cbd2d71002223cda5330f294c950d80.

Ignore lines with "in function" and "In function" (#534)

In recent binutils version, the warning, for stubbed functions, is
properly printed and due to this correction, linking a project with
stubbed functions fails the build in headless build rather than
just printing the warnings.

Example:
.../arm-none-eabi/bin/ld.exe: .../libc.a(libc_a-writer.o): in function `_write_r':
(.text._write_r+0x10): warning: _write is not implemented and will always fail
...
12:02:52 Build Failed. 8 errors, 8 warnings. (took 6s.284ms)

The first line matches the error pattern (.*[/\\])?ld(\.exe)?: (.*)
that incorectly fails the build in headless mode (a single line matching
a pattern with severity "error" fails the build) when there are really
only warnings in the build log.

The problem can be obsered using the GCC 11 (and later) toolchain
builds with newlib for the arm-none-eabi target provided by Arm.

Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>

Remove old Orbit in Oomph p2 repo from setup (#524)

The https://download.eclipse.org/oomph/simrel-orbit/ was the temporary
URL.

Add commons-io (#537)

Fixes #536

Updated dependencies in preparation for 11.3.0 RC2 (#538)

Part of #420

CMake: Fixed the correct path for starting 'cmake-gui'

This PR fixed the wrong source flag which was set by spawning the cmake-gui command.

Closes #532

Remove standalone publishing from promote-a-build

The CDT project stopped publishing standalone separately
2 1/2 years ago:

https://github.com/eclipse-cdt/cdt/blob/main/NewAndNoteworthy/CDT-10.2.md#cdt-standalone-debugger-part-of-main-download

and as there has been no call for it since then this commit
removes the remnants of the publishing script.

Add cdt-lsp support to the promote-a-build scripts

Part of https://github.com/eclipse-cdt/cdt-lsp/issues/197

Include latest CDT milestone in cdt.target (#541)

Use final URLs for 2023-09 dependencies

Part of #420

Composites for CDT 11.3 release

Part of #420