Improve log4j2 configuration for cx-client-common

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,31 @@
+---
+name: Report an issue
+about: Create a bug report to fix an existing issue.
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+### Description
+
+> Provide a description of the issue
+
+### Expected Behavior
+
+### Actual Behavior
+
+### Reproduction
+
+> Detail the steps taken to reproduce the issue
+> 
+> Where applicable, please include (exclude sensitive information):
+>
+> - Code of Files to reproduce the issue
+> - Log files
+> - Application settings
+> - Screenshots
+
+### Environment Details
+
+> Provide any information relating to the environment the issue was identified in - include applicable version and additional runtime information (include OS or other underlying infrastructure)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest new functionality for this project.
+title: ''
+labels: 'enhancement'
+assignees: ''
+
+---
+
+### Describe the problem
+
+> A clear description of what the problem is.
+
+### Proposed solution
+
+> A clear description of what you want to happen.
+
+### Additional details
+
+> Add any other details / contexts / screenshots about the feature request.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+By submitting a PR to this repository, you agree to the terms within the [Checkmarx Code of Conduct](https://github.com/checkmarx-ltd/open-source-template/blob/master/CODE-OF-CONDUCT.md). Please see the [contributing guidelines](https://github.com/checkmarx-ltd/open-source-template/blob/master/CONTRIBUTING.md) for how to create and submit a high-quality PR for this repo.
+
+### Description
+
+> Describe the purpose of this PR along with any background information and the impacts of the proposed change.
+
+### References
+
+> Include supporting link to GitHub Issue/PR number
+
+### Testing
+
+> Describe how this change was tested. Be specific about anything not tested and reasons why. If this solution has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
+>
+> Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
+
+### Checklist
+
+- [ ] I have added documentation for new/changed functionality in this PR (if applicable).  *If documentaiton is a Wiki Update, please indicate desired changes within PR MD Comment*
+- [ ] All active GitHub checks for tests, formatting, and security are passing
+- [ ] The correct base branch is being used

.github/release-drafter.yml

@@ -0,0 +1,32 @@
+name-template: 'v$RESOLVED_VERSION 🌈'
+tag-template: 'v$RESOLVED_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bugfix'
+      - 'bug'
+  - title: '🧰 Maintenance'
+    label: 'chore'
+exclude-labels:
+  - 'skip-release-notes'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+version-resolver:
+  major:
+    labels:
+      - 'major'
+  minor:
+    labels:
+      - 'minor'
+  patch:
+    labels:
+      - 'patch'
+  default: patch
+template: |
+  ## Changes
+
+  $CHANGES

.github/workflows/release-drafter.yml

@@ -0,0 +1,19 @@
+name: Release Drafter
+
+on:
+  push:
+    # branches to consider in the event; optional, defaults to all
+    branches:
+      - master
+
+jobs:
+  update_release_draft:
+    runs-on: ubuntu-latest
+    steps:
+      # Drafts your next Release notes as Pull Requests are merged into "master"
+      - uses: release-drafter/release-drafter@v5
+        with:
+          # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
+          config-name: release-drafter.yml
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -1,5 +1,6 @@
 work/
 out/
+*-secrets.properties
 
 #Gradle
 .gradle/
@@ -19,3 +20,4 @@ bin/
 #Jenkins specific out
 *.hpi
 classes/
+*.dummy

CONTRIBUTING.md

@@ -0,0 +1,77 @@
+# Contributing to Checkmarx projects
+
+Welcome and thank you for considering contributing to a Checkmarx open source project.
+
+Reading and following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing these open source projects. In return, we will reciprocate that respect by addressing your issue, assessing changes, and helping you finalize your pull requests.
+
+
+## Quicklinks
+
+- [Contributing to Checkmarx projects](#contributing-to-checkmarx-projects)
+  - [Quicklinks](#quicklinks)
+  - [Code of Conduct](#code-of-conduct)
+  - [Getting Started](#getting-started)
+  - [Issues](#issues)
+  - [Pull Requests](#pull-requests)
+  - [Resources](#resources)
+
+## Code of Conduct
+
+By participating and contributing to any Checkmarx projects, you agree to uphold our [Code of Conduct](https://github.com/checkmarx-ltd/open-source-template/blob/master/CODE-OF-CONDUCT.md).
+
+## Getting Started
+
+If you have suggestions for how this project could be improved, or want to report a bug, open an issue. We appreciate all contributions. If you have questions, we'd love to hear them.
+
+We also appreciate PRs.  If you're thinking of submitting any PR, pleae open an issue first to spark a discussion around it.
+
+Contributions are made to this repo via Issues and Pull Requests (PRs).  A few general guidelines that cover both:
+
+- Search for existing Issues and PRs before creating your own to avoid duplicates.
+- PRs will only be accepted if associated with an issue (enhancement or bug) that has been submitted and reviewed/labeld as *accepted* by a Checkmarx team member.
+- We will work hard to makes sure issues that are raised are handled in a timely manner.
+
+## Issues
+
+Issues should be used to report problems with the solution / source code, request a new feature, or to discuss potential changes before a PR is created. When you create a new Issue, a template will be loaded that will guide you through collecting and providing the information we need to investigate.
+
+If you find an Issue that addresses the problem you're having, please add your own reproduction information to the existing issue rather than creating a new one. Adding a [reaction](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) can also help by indicating to our maintainers that a particular problem is affecting more than just the reporter.
+
+### Templates
+
+The following templates will be used within Checkmarx github repositories
+- [Enhancement/Feature Request Template](.github/ISSUE_TEMPLATE/feature_request.md)
+- [Bug Report Template](.github/ISSUE_TEMPLATE/bug_report.md)
+
+## Pull Requests
+
+PRs to our source are always welcome and can be a quick way to get your fix or improvement slated for the next release. In general, PRs should:
+
+- Only fix/add the functionality in question **or** address code style issues, not both.
+- Ensure all necessary details are provided and adhered to
+- Add unit or integration tests for fixed or changed functionality (if a test suite already exists) or specify steps taken to ensure changes were tested and functionality works as expected.
+- Address a single concern in the least number of changed lines as possible.
+- Include documentation in the repo or Provide additional comments in Markdown comments that should be pulled/reflected in GitHub Wiki for the given project. 
+- Be accompanied by a complete Pull Request template (loaded automatically when a PR is created).
+
+For changes that address core functionality or would require breaking changes (e.g. a major release), please open an Issue to discuss your proposal first. 
+
+In general, we follow the _fork-and-pull_ Git workflow
+
+1. Fork the repository to your own Github account
+2. Clone the project to your machine
+3. Create a branch locally with a succinct but descriptive name (prefix with feature/<issue#>-descriptive-name> or hotfix/<issue#>-descriptive-name)
+4. Commit changes to the branch
+5. Push changes to your fork
+6. Open a PR in our repository and follow the PR template so that we can efficiently review and asses the changes.  *Ensure an associated Issue has been accepted by the Checkmarx team.*
+
+### Templates
+The following template will be used within Checkmarx github repositories
+
+[Pull Request Template](.github/PULL_REQUEST_TEMPLATE.md)
+
+## Resources
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
+- [GitHub Help](https://help.github.com)