Produce an uber jar on release
nikitawootten-nist opened this issue · 3 comments
User Story:
As a user of the OSCAL CLI, I would like accessible means to using the OSCAL CLI without relying on Maven or building the project locally.
Goals:
- Clear guidance on how to produce an uber jar locally
- Produce an uber jar as part of the release action
- Clear guidance on how to run the CLI from an uber jar
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.
@nikitawootten-nist thanks for submitting this issue. I believe we talked about this before and you had experimented with building your own Uber jar on a fork somewhere. Can you send that along? Would you be interested in taking up this work?
I can take this up. Should we add it to this sprint?
I can take this up. Should we add it to this sprint?
You may proceed. I am not going to formally add it to the sprint yet, but I will add it the backlog. If you feel you have capacity to bring it in to sprint while working other tasks or waiting on others/blockers, I welcome it. :-)