Release of SLIM Java Starterkit Sample Project

[jpl-jengelke]

Purpose

• Release of a unified Java sample project starterkit that automates build, release and publishing to Maven Central for OSS consumption.

Proposed Changes

• NOTE: Build instructions are inline with the project README.
• Introduction of a feature rich Java project template that provides the following:
  • Dependency tracking and easy version updating using property placeholders
  • Project inheritance via shared settings in the parent-ammos POM
  • Maven CI-friendly build tooling
    • Developer responsibility for Major/Minor/Patch version numbering
    • Implement chain-of-custody tracking with hash/version/build markers from repository to release
    • Version is stamped into a file named version in the top-level of produced artifacts, such as JARs or WARs
    • Fast, efficient: Eliminate redundancy of Release Plugin
  • GitHub Action publishing end-to-end on PR push to main branch.
    • Tag and release and upload to Maven Central occurs without further manual intervention.
  • Tooling for continuous integration, continuous testing and security scanning on different platforms, including Jenkins and GitHub Actions.
  • Instructions for both local development installations and build/package/release installations.

Issues

• [Improve Best Practice Guide]: Continuous integration (SK) through Jenkins, et. al. slim#23: Universal Jenkinsfile templates tested for continuous integration.
• [Improve Best Practice Guide]: Unit testing, et. al. slim#24: Example unit testing using JUnit standard setup.
• [Improve Best Practice Guide]: Security scanning with SCRUB, et. al. slim#25: Security scanning automation using NASA SCRUB.
• [New Best Practice Guide]: Code Coverage slim#104: Code coverage automation using NASA SCRUB.
• [New Best Practice Guide]: Continuous Testing Guide and Checklist slim#110: Sample continuous testing implementation for JUnit 4 unit tests.
• [New Process Improvement Need]: Java-based project to integrate with GitHub Actions, Maven Central, etc. slim#127: This is the culmination of the Java starterkit template.

Testing

• Local build and installation
• Successful execution of tag/release cycle on local Maven repository
• Validation of expectations in GitHub Actions build cycle

[jpl-jengelke]

Notification will be sent when converted from draft status.

[yunks128]

Using chmod 777 on the user's home directory (${HOME}) might be too permissive.
How about chown instead?
chown -R ${USR}:${USR} ${HOME}

[jpl-jengelke]

That's a great observation. It is running inside the container so I was assuming this was only affecting the mount inside the container. In this context, the container is only executed ephemerally and stops after the job completes. I definitely need to review some of this earlier stuff to tighten it up, so I will.

Please bear with me as there will be more content to review shortly. I've kept it in draft until it's ready for thorough review.