Update references to master branch (replaced with main) (#388)

Part of #384

.github/workflows/licensecheck.yml

@@ -5,10 +5,10 @@ name: License vetting status check
 on:
   push:
     branches: 
-      - 'master'
+      - 'main'
   pull_request:
     branches: 
-     - 'master'
+     - 'main'
   issue_comment:
     types: [created]
 

CONTRIBUTING.md

@@ -20,7 +20,7 @@ To try out and develop the plug-ins in you can edit and run them from source.
 All PRs are built using GitHub Actions using the workflows in the [.github/workflows](.github/workflows) directory.
 
 All branches are built using the [Jenkinsfile](Jenkinsfile) on the [Eclipse Foundations Jenkins infrastructure](https://wiki.eclipse.org/Jenkins) in the [cdt-lsp](https://ci.eclipse.org/cdt/job/cdt-lsp) multi-branch pipeline.
-The pipeline publishes continuously to download.eclipse.org, for example the `master` branch publishes to https://download.eclipse.org/tools/cdt/builds/cdt-lsp/master/
+The pipeline publishes continuously to download.eclipse.org, for example the `main` branch publishes to https://download.eclipse.org/tools/cdt/builds/cdt-lsp/main/
 
 ## CI Milestone and Release Builds
 

README.md

@@ -4,7 +4,7 @@
 
 This plugin is based on the [LSP4E](https://github.com/eclipse/lsp4e) and [TM4E](https://github.com/eclipse/tm4e) Eclipse projects. The editor is based on the [`ExtensionBasedTextEditor`](https://github.com/eclipse-platform/eclipse.platform.ui/blob/master/bundles/org.eclipse.ui.genericeditor/src/org/eclipse/ui/internal/genericeditor/ExtensionBasedTextEditor.java#L55-L56) in Eclipse.
 
-The [`org.eclipse.cdt.lsp`](https://github.com/eclipse-cdt/cdt-lsp/tree/master/bundles/org.eclipse.cdt.lsp) is the core plugin. C/C++ IDE Developers can use the [`serverProvider`](https://github.com/eclipse-cdt/cdt-lsp/blob/master/bundles/org.eclipse.cdt.lsp/schema/serverProvider.exsd) extension point to define a C/C++ language server. If there is no extension defined, the LLVM [clangd](https://clangd.llvm.org/) language server will be used and searched on the PATH environment variable. Clangd searches for a `compile_commands.json` file in the source file folder and its parents. It's needed to determine the compile informations. In the default clangd configuration, the PATH will be searched for a `gcc` compiler to determine the default compiler include paths.
+The [`org.eclipse.cdt.lsp`](https://github.com/eclipse-cdt/cdt-lsp/tree/main/bundles/org.eclipse.cdt.lsp) is the core plugin. C/C++ IDE Developers can use the [`serverProvider`](https://github.com/eclipse-cdt/cdt-lsp/blob/main/bundles/org.eclipse.cdt.lsp/schema/serverProvider.exsd) extension point to define a C/C++ language server. If there is no extension defined, the LLVM [clangd](https://clangd.llvm.org/) language server will be used and searched on the PATH environment variable. Clangd searches for a `compile_commands.json` file in the source file folder and its parents. It's needed to determine the compile informations. In the default clangd configuration, the PATH will be searched for a `gcc` compiler to determine the default compiler include paths.
 
 The editor is basically the `ExtensionBasedTextEditor`. The language grammar comes from [TM4E](https://github.com/eclipse/tm4e). 
 
@@ -98,7 +98,7 @@ see [issues](https://github.com/eclipse-cdt/cdt-lsp/issues)
 1. Download the latest Developer Build of Eclipse for C/C++ Developers or Eclipse for Embedded C/C++ Developers using the [Eclipse installer](https://www.eclipse.org/downloads/packages/installer) or downloading and extracting the latest release available on [eclipse.org](https://www.eclipse.org/downloads/packages/release/).
 2. Add to your Available Software Sites and install *C/C++ LSP Support* in the *Eclipse CDT LSP* Category and restart Eclipse from one of these p2 sites:
     - For latest release: `https://download.eclipse.org/tools/cdt/releases/cdt-lsp-latest`
-    - For current master branch continuous build: `https://download.eclipse.org/tools/cdt/builds/cdt-lsp/master/`
+    - For current main branch continuous build: `https://download.eclipse.org/tools/cdt/builds/cdt-lsp/main/`
 3. [Install Pre-requisites](#install-pre-requisites) listed below
 4. [Create a CMake project](#create-an-example-cmake-project) or [import an existing](#import-an-existing-project) project following guidelines below
 5. [Enable the LSP based C/C++ Editor](#activating-lsp-based-cc-editor) following instructions above.

RELEASING.md

@@ -4,30 +4,30 @@ This is the Release plan and TODO list for CDT LSP.
 
 Items at the beginning of development
 
-- [ ] Create an Endgame Issue to track the release. As a starting point use [RELEASING.md](https://github.com/eclipse-cdt/cdt-lsp/blob/master/RELEASING.md).
+- [ ] Create an Endgame Issue to track the release. As a starting point use [RELEASING.md](https://github.com/eclipse-cdt/cdt-lsp/blob/main/RELEASING.md).
     - [ ] Add the [Endgame](https://github.com/eclipse-cdt/cdt-lsp/labels/endgame) label
 - [ ] Create a [New milestone](https://github.com/eclipse-cdt/cdt-lsp/milestones/new) for the release, and if available add a due date 
     - [ ] Apply the milestone to the endgame issue
 - [ ] Ensure all previous [Endgame issues](https://github.com/eclipse-cdt/cdt-lsp/labels/endgame) are done.
-    - [ ] Make sure any previous edits made to [Endgame issues](https://github.com/eclipse-cdt/cdt-lsp/labels/endgame) of previous releases are updated in [RELEASING.md](https://github.com/eclipse-cdt/cdt-lsp/blob/master/RELEASING.md)
-- [ ] Update version numbers on master branch (after the release branch was created), this is generally the next minor version (or major version if that is what the committers on the project agree) and applies to the following types of files:
+    - [ ] Make sure any previous edits made to [Endgame issues](https://github.com/eclipse-cdt/cdt-lsp/labels/endgame) of previous releases are updated in [RELEASING.md](https://github.com/eclipse-cdt/cdt-lsp/blob/main/RELEASING.md)
+- [ ] Update version numbers on main branch (after the release branch was created), this is generally the next minor version (or major version if that is what the committers on the project agree) and applies to the following types of files:
     - [ ] `feature.xml` version
     - [ ] `pom.xml` version
     - It does not apply to versions in MANIFEST.MF which follow [API rules](https://github.com/eclipse-cdt/cdt/blob/main/POLICY.md#api).
-- [ ] Ensure [the CI build](https://ci.eclipse.org/cdt/job/cdt-lsp/job/master/) is stable - it is always better to release a "Green Dot" build
+- [ ] Ensure [the CI build](https://ci.eclipse.org/cdt/job/cdt-lsp/job/main/) is stable - it is always better to release a "Green Dot" build
 
 Items in the days ahead of Release day:
 
 - [ ] Create release on [PMI](https://projects.eclipse.org/projects/tools.cdt) (e.g. `1.0.0 (CDT LSP)`)
-    - [ ] Fill in the *Review Documentation* -> *New & Noteworthy URL* with the [CHANGELOG.md](https://github.com/eclipse-cdt/cdt-lsp/blob/master/CHANGELOG.md)
-- [ ] Check [CHANGELOG.md](https://github.com/eclipse-cdt/cdt-lsp/blob/master/CHANGELOG.md) is up to date. The changelog should have a version entry, release date, API Breakages and other information consistent with current entries in the changelog.
-- [ ] Check [README.md](https://github.com/eclipse-cdt/cdt-lsp/blob/master/README.md) is up to date, in particular:
+    - [ ] Fill in the *Review Documentation* -> *New & Noteworthy URL* with the [CHANGELOG.md](https://github.com/eclipse-cdt/cdt-lsp/blob/main/CHANGELOG.md)
+- [ ] Check [CHANGELOG.md](https://github.com/eclipse-cdt/cdt-lsp/blob/main/CHANGELOG.md) is up to date. The changelog should have a version entry, release date, API Breakages and other information consistent with current entries in the changelog.
+- [ ] Check [README.md](https://github.com/eclipse-cdt/cdt-lsp/blob/main/README.md) is up to date, in particular:
     - [ ] the planned release and which versions of main dependencies are supported in the version support table
     - [ ] screenshots are up to date and consistent
     - [ ] try it out steps are correct and where suitable versions are up to date
 - [ ] Check all closed PRs and Issues to make sure their milestone is set. [This search may be useful to identify such closed issues](https://github.com/eclipse-cdt/cdt-lsp/issues?q=is%3Aclosed)
 - [ ] Create a branch for the release
-- [ ] Create the endgame for the next scheduled release right away and update the versions on the master branch
+- [ ] Create the endgame for the next scheduled release right away and update the versions on the main branch
 
 Items on Release day: