Downgraded to java 11 (#9)

Also updated some plugins.
Added some new workflows

.github/ FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: [ RealYusufIsmail ]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+[code_of_conduct]: https://github.com/realyusufismail/jconfig/blob/master/.github/CODE_OF_CONDUCT.md
+
+[new_issue]: https://github.com/realyusufismail/jconfig/issues/new/choose
+
+## Pull Request Etiquette
+
+<!--
+  There are several guidelines you should follow in order for your
+  Pull Request to be merged.
+-->
+
+- [ ] I have checked the PRs for upcoming features/bug fixes.
+- [ ] I have read the [code of conduct][code_of_conduct].
+
+<!--
+  It is sometimes better to include more changes in a single commit. 
+  If you find yourself having an overwhelming amount of commits, you
+  can **rebase** your branch.
+-->
+
+### Changes
+
+- [ ] Internal code
+- [ ] Library interface (affecting end-user code)
+- [ ] Documentation
+- [ ] Other: \_____ <!-- Insert other type here -->
+
+<!-- Replace "NaN" with an issue number if this is a response to an issue -->
+
+Closes : NaN
+
+## Description
+
+Replace this sentence with general description of what your Pull Request does.

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,102 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for
+everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity
+and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion,
+or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take
+appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing
+the community in public spaces. Examples of representing our community include using an official e-mail address, posting
+via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible
+for enforcement at yusufgamer222@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem
+in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the
+community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation
+and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
+unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
+interactions in community spaces as well as external channels like social media. Violating these terms may lead to a
+temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
+period of time. No public or private interaction with the people involved, including unsolicited interaction with those
+enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate
+behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired
+by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/ISSUE_TEMPLATE/ feature_request.yml

@@ -0,0 +1,39 @@
+name: Feature Request
+description: Request a new feature
+labels: [ enhancement ]
+assignees: [ RealYusufIsmail ]
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        Please ask questions in [our Discussions](https://github.com/realyusufismail/jconfig/discussions)
+        
+        Keep in mind that this isn't the place to learn Kotlin.  
+        Please head over to [StackOverflow](https://stackoverflow.com/questions/tagged/kotlin) for your general programming questions.
+  - type: checkboxes
+    attributes:
+      label: General Troubleshooting
+      description: You confirm to have made the following checks first.
+      options:
+        - label: I have checked for similar issues on the Issue-tracker.
+          required: true
+        - label: I have updated to the [latest JConfig version](https://search.maven.org/artifact/io.github.realyusufismail/ydwk)
+          required: true
+        - label: I have checked the branches or the maintainers' PRs for upcoming features.
+          required: true
+  - type: textarea
+    attributes:
+      label: "Feature Request"
+      description: "Provide a small description of the feature you want to have added."
+      placeholder: "JConfig should get ..."
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: "Example Use-Case"
+      description: |-
+        Provide some code or describe a possible use-case for this feature.
+        
+        The provided text will be rendered as Kotlin code, so you don't have to provide a Code block for it.
+      placeholder: "fun newMethod() { ... }"
+      render: kotlin

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,51 @@
+name: Bug reports
+description: Create a report to help us improve
+labels: [ bug ]
+assignees: [ RealYusufIsmail ]
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        Please ask questions in [our Discussions](https://github.com/realyusufismail/jconfig/discussions)
+        
+        Keep in mind that this isn't the place to learn Kotlin.  
+        Please head over to [StackOverflow](https://stackoverflow.com/questions/tagged/kotlin) for your general programming questions.
+
+        Also try to search for your issue - it may have already been answered or even fixed.
+        However, if you find that an old, closed issue still persists in the latest version,
+        you should open a new issue using the form below instead of commenting on the old issue.
+  - type: checkboxes
+    attributes:
+      label: General Troubleshooting
+      description: You confirm to have made the following checks first.
+      options:
+        - label: I have checked for similar issues on the Issue-tracker.
+          required: true
+        - label: I have updated to the [latest JConfig version](https://search.maven.org/artifact/io.github.realyusufismail/jconfig)
+          required: true
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps to reproduce
+      description: |
+        What do we need to do in order to make the bug happen? Clear and concise reproduction instructions are important for us to be able to triage your issue in a timely manner. Note that you can use [Markdown](https://guides.github.com/features/mastering-markdown/) to format lists and code.
+      placeholder: Steps to reproduce
+    validations:
+      required: false
+  - type: textarea
+    id: expected
+    attributes:
+      label: What is expected?
+    validations:
+      required: true
+  - type: textarea
+    id: actually-happening
+    attributes:
+      label: What is actually happening?
+    validations:
+      required: true
+  - type: textarea
+    id: additional-comments
+    attributes:
+      label: Any additional comments?
+      description: e.g. some background/context of how you ran into this bug.

.github/workflows/ release.yml

@@ -0,0 +1,34 @@
+# Whenever a commit is pushed with a non-snapshot version (no "-SNAPSHOT" suffix), this job will create a new
+# GitHub release. Additionally, it will increment the version by one patch level, append a "-SNAPSHOT" suffix, and
+# commit + push it to release branch (e.g., "0.0.2" -> "0.0.3-SNAPSHOT").
+# Automatically merge release PR
+name: Release and Update
+on:
+  push:
+    branches:
+      - 'master'
+jobs:
+  release:
+    name: Create Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v3
+      - name: Read Version
+        id: read-version
+        run: |
+          version=`cat gradle.properties | sed -n "s/^.*version\s*=\s*\(\S*\).*$/\1/p"`
+          echo "::set-output name=version::$version"
+      - name: Create Release
+        if: ${{ !endsWith(steps.read-version.outputs.version, 'SNAPSHOT') }}
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: v${{ steps.read-version.outputs.version }}
+          release_name: v${{ steps.read-version.outputs.version }}
+          body: |
+            Version ${{ steps.read-version.outputs.version }}
+          draft: true
+          prerelease: false

.github/workflows/ snapshot.yml

@@ -0,0 +1,26 @@
+# If the version contains the SNAPSHOT suffix it will run publishYdwkPublicationToMavenCentralRepository
+name: Snapshot
+on:
+  push:
+    branches:
+      - 'master'
+
+jobs:
+  snapshot:
+    name: Create Snapshot
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v3
+      - name: Read Version
+        id: read-version
+        run: |
+          version=`cat gradle.properties | sed -n "s/^.*version\s*=\s*\(\S*\).*$/\1/p"`
+          echo "::set-output name=version::$version"
+      - name: Run maven snapshot
+        if: ${{ endsWith(steps.read-version.outputs.version, 'SNAPSHOT') }}
+        run: |
+          ./gradlew publishJconfigPublicationToMavenCentralRepository
+        env:
+          MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.MAVEN_PASSWORD }}