OSCAL XML and JSON Schemas incorrectly packaged after generated in build #171
Comments
aj-stein-nist
added a commit
that referenced
this issue
Aug 13, 2023
aj-stein-nist
added a commit
that referenced
this issue
Aug 14, 2023
|
This was fixed in the v3.0.1 release. Updating accordingly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
As reported in usnistgov/oscal-cli#176, there is an issue with that application depending on this library because the requisite JSON and XML schemas generated during the build, but not the path to pull them into resources for the package is incorrect. Therefore, they are not packaged.
Who is the bug affecting?
Any developer relying on liboscal-java
What is affected by this bug?
Any developer relying on liboscal-java to write XML and JSON schemas validation using the embedded schemas for a given OSCAL version.
When does this occur?
Consistently
How do we replicate the issue?
See oscal-cli#176 for how a dependent application will use library functions looking for the embedded schemas for validation functions and fail.
Expected behavior (i.e. solution)
The resources are properly embedded (doesn't work) after generation (that works) at
target/generated-resources/oscal, nottarget/generated-resources/metaschema-schemas.Other Comments
N/A
The text was updated successfully, but these errors were encountered: