Nightly snapshot builds of develop and feature branches

[aj-stein-gsa]

User Story

As a developer of Metaschema-enabled tools and data, in order to more effectively test pre-release builds of this library, I would like snapshot builds of the library from develop (and possibly relevant feature* branches, if possible) published to metaschema-framework/maven2.

Goals

• Make developer testing faster for tighter feedback loops
• Allow dependent libraries and applications able to use snapshot builds locally or in CI/CD without building this library as a dependency itself

Dependencies

N/A

Acceptance Criteria

• All website and readme documentation affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

Revisions

No response

[david-waltermire]

Doing nightly snapshots in m-j is not needed for develop, since snapshots are created when new commits are added to m-j. Where this is actually needed is in l-o-j, and o-c to test new m-j snapshots. This is somewhat straight forward to do on develop in these repos. Doing this for feature branches is more involved due to how Maven produces build artifact names. We would need to work out how to incorporate the branch name into the Maven build process.

Thoughts?

[aj-stein-gsa]

Doing nightly snapshots in m-j is not needed for develop, since snapshots are created when new commits are added to m-j. Where this is actually needed is in l-o-j, and o-c to test new m-j snapshots.

That is a good point.

This is somewhat straight forward to do on develop in these repos. Doing this for feature branches is more involved due to how Maven produces build artifact names. We would need to work out how to incorporate the branch name into the Maven build process.

Thoughts?

Thanks for the reminder. I had spent some time thinking about this facet of the deployment and how it work with Maven and read a lot, and did not find anything conclusive. I went done a rabbit hole on that and hadn't circled back. Is that worth doing then or we only focus on builds from develop for now and avoid the complexity of it?

(I think @wandmagic and I are the only people who would use it frequently, so I ping him for his take.)

[aj-stein-gsa]

Also, after we discuss that, I can close this out in favor of metaschema-framework/liboscal-java#110 and metaschema-framework/oscal-cli#104 because the work will not be happening here exactly, but I assume we want to make a decision on ☝ and then act on it elsewhere.