(#186) Add Docker-based test setup to run in GitHub

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: AFaust
+type: Bug
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+ - ACS version [e.g. 26.1]
+ - OOTBee version [e.g. 1.2.3.1]
+
+**Additional details**
+Since OOTBee Support Tools is an addon for administrative and/or development users, you might be able to provide more technical details. We appreciate any log output from e.g. `alfresco.log` or your browser's web developer tools console, insights from potential tests of different configuration variants, or even code analysis.
+
+**Additional context**
+Add any other context about the problem here.
+
+**Contribution**
+Let us know if and how you may be able to contribute to resolving the bug.
+- If you write code and can code up the solution, we welcome PRs. If you can do this but would like guidance from the core team let us know.
+- Are you willing/able to test any work we do towards your request?
+- If you plan to contribute to the project and you are not familiar with our current [contribution policy](https://github.com/OrderOfTheBee/ootbee-support-tools/blob/master/CONTRIBUTING.md), please make sure you have read that document.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: AFaust
+
+---
+
+**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 or screenshots about the feature request here.
+
+**Contribution**
+Let us know if and how you may be able to contribute to resolving the request.
+- If you write code and can code up the solution, we welcome PRs. If you can do this but would like guidance from the core team let us know.
+- Are you willing/able to test any work we do towards your request?
+- If you plan to contribute to the project and you are not familiar with our current [contribution policy](https://github.com/OrderOfTheBee/ootbee-support-tools/blob/master/CONTRIBUTING.md), please make sure you have read that document.

.github/PULL_REQUEST_TEMPLATE/default.md

@@ -0,0 +1,30 @@
+### CHECKLIST
+
+We will not consider a PR until the following items are checked off--thank you!
+
+- [ ] There aren't existing pull requests attempting to address the issue mentioned here
+- [ ] Submission developed in a feature branch--not master
+
+### CONVINCING DESCRIPTION
+
+... Describe the changes provided by this PR...
+
+### RELATED INFORMATION
+
+... If you have any supporting material such as issues that are addressed by this
+PR, links outlining any special techniques or libraries used, etc that will help
+us to evaluate this PR. Please include that information here...
+
+Fixes #
+
+# BE WARNED
+
+- If any of the checklist items are missed, incomplete or invalid we will not accept the PR
+- If you are not responsive to feedback on your PR we will not accept the PR
+- If we do not accept your PR we will provide feedback on the PR indicating why
+- After some time, we will close PRs that have not been accepted
+
+When we decline or close your PR. You are encouraged to address the concerns outlined in the
+PR and then re-submit it. We want contributions. We also need for them to be of high quality
+and high value and to not take undue resources away from the features and enhancements the
+core team is working on. Thanks for understanding!

.github/workflows/build.yaml

@@ -21,15 +21,29 @@ on:
 
 jobs:
   build:
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v3
-      - name: Set up JDK 8
-        uses: actions/setup-java@v3
+      - uses: actions/checkout@v4
+      - uses: actions/setup-java@v4
         with:
-          java-version: '8'
           distribution: 'temurin'
           cache: 'maven'
-      - name: Build with Maven
-        run: mvn --batch-mode --update-snapshots package
+          java-version: |
+            8
+            11
+            17
+            21
+      - run: mvn -version
+      - run: mvn --batch-mode --update-snapshots package
+# Tried running version tests in parallel but this caused failures with Java tools.jar reference
+      - id: build-and-test-6-1
+        run: mvn --batch-mode verify -Pgithub-test
+      - id: build-and-test-7-4
+        run: mvn --batch-mode verify -Pgithub-test,acs-docker-7.4
+      - id: build-and-test-23-1
+        run: mvn --batch-mode verify -Pgithub-test,acs-docker-23.1
+      - id: build-and-test-25-1
+        run: mvn --batch-mode verify -Pgithub-test,acs-docker-25.1
+      - id: build-and-test-26-1
+        run: mvn --batch-mode verify -Pgithub-test,acs-docker-26.1