Add support for Github Actions plus cleanup and updates to POM files

[JeremyMcCormick]

This PR implements Github Actions for hps-java CI/CD.

The new workflows are as follows:

• deploy - Deploys the snapshot (development) jars whenever the master branch is updated
• release - Performs the Maven release, creates the Github release page, (optionally) updates the project website, and bumps the development version
• site - Deploys the project website to gh-pages
• test - Runs the tests for PRs (replaces the old maven.yml workflow file)

All of these can be run manually through the "Actions" tab in the project.

Additionally, I made a cleanup pass on all the project POM files and some other project configuration, including the following:

• Updated all Maven plugins to their current release versions
• Changed deployment so it only uploads the bin jar rather than the jars for every module (which never made much sense as they are not really used as independent artifacts by other projects)
• Moved all module dependency versions into the dependencyManagement section of the main POM
• Removed outdated or unused configuration and plugins from the main POM
• Updated SCM settings for usage on Github
• Removed unwanted dependency on jdom 1.0 which was conflicting with 1.1
• Simplified and cleaned up the project website
• Removed old collaborator contact information
• Added a log4j config to remove warning messages from the tests

My TODO list before un-drafting:

• Replace "JeremyMcCormick" user with "JeffersonLab" group in all workflows and POM configuration
• Add a deployment key and its private key as a secret
• Add the CI deployment username and password secrets
• Change the development release to match hps-java/master branch (should be 5.2.0-SNAPSHOT)
• Confirm that running the release workflow with tests works on the fork without errors
• Confirm that the site workflow works correctly on the branch and that the site navigation works correctly in gh-pages

After being approved, this should be merged to master as a "squash commit" to avoid unwanted messages from the branch history (from merge commits, test releases, etc.).

[sarahgaiser]

Is this still an active todo?

[JeremyMcCormick]

I can do this later in another PR.

…

On Tue, Sep 5, 2023 at 1:26 PM sarahgaiser ***@***.***> wrote: ***@***.**** approved this pull request. ------------------------------ In .github/workflows/release.yml <#975 (comment)> : > + default: true + deploy_site: + description: "Update the project website" + required: false + type: boolean + default: true + secrets: + SSH_PRIVATE_KEY: + required: true + CI_DEPLOY_USERNAME: + required: true + CI_DEPLOY_PASSWORD: + required: true + +jobs: + # TODO: Add test here for a sanity check Is this still an active todo? — Reply to this email directly, view it on GitHub <#975 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQXV42W4HFEHPZ7DYAUP3DXY5VEVANCNFSM6AAAAAAWURLTDI> . You are receiving this because you authored the thread.Message ID: ***@***.***>