…plugin to v3.3.1

…gin to v3.2.3

…ch-null-default

Add support for `case null, default` in switch and fix concrete syntax model for new switch syntax

…gin to v3.4.0

…gin to v2.1.0

Refact: Adds a find node by range method in Node class

…gin to v3.2.4

…ch-patterns

[JEP441] Add support for switch pattern matching

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.2 to 4.1.3.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4.1.2...v4.1.3)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

…actions/actions/checkout-4.1.3

chore(deps): bump actions/checkout from 4.1.2 to 4.1.3

…gin to v3.4.1

…ion methods

…nd-readme

✏️ make mvnw command runnable by copy-pasting

Fix: Fixes the version currently supported by Javaparser.

….16.0

…plugin to v3.1.2

…-plugin to v3.1.2

Fix issue 2368 Unable to calculate the type of a varargs parameter

…ingPrinter

Minor refactoring on Concrete syntax model

…rd-patterns

PatternExpr -> TypePatternExpr refactor in preparation for record pattern implementation

Improve unit test on generic

settings.localRepository might contains spaces, which splits the
arguments once passed to the commande line in Maven. We use single
quotes to keep them together as one single argument.

Notice that double quotes did not fix the issue, although many resources
on the Web suggest to use double quotes for similar issues.

Fixes javaparser#4410

Currently, any value can be provided at compile time, including
incompatible ones. A compatibility check is then executed at runtime on
line 111.

By using generics on the constructor, we ask the compiler to do this
check for us. Consequently, the check is done immediately (compile time)
and the runtime check of line 111 becomes irrelevant.

For example, in the previous commit, while replacing the
END_OF_LINE_CHARACTER value from SYTEM_EOL (String) to
LineSeparator.SYSTEM (LineSeparator), the type incompatibility was only
spotted upon running the tests (which massively exploded), making me fix
it by using LineSeparator.SYSTEM.asRawString() (String). Now we know the
discrepancy immediately from the compiler, before to run any test.

Fixes SYSTEM_EOL warnings

…codegen

Fix missed generated code from PatternExpr refactor

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.4 to 4.1.5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4.1.4...v4.1.5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Test added.

…actions/actions/checkout-4.1.5

chore(deps): bump actions/checkout from 4.1.4 to 4.1.5

…-static

Fix: <enum>::values() is a static method, was not static