Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release of version 1.13.0 #66

Merged
merged 30 commits into from
Oct 14, 2024
Merged

Prepare release of version 1.13.0 #66

merged 30 commits into from
Oct 14, 2024

Conversation

bertrand-lorentz
Copy link
Contributor

No description provided.

bertrand-lorentz and others added 30 commits July 16, 2024 11:10
Also add the corresponding NTDs in the unit test data.
Add voluntary forms to expected notice subtypes (TEDEFO-3556)
Also update to the latest version.
This plugin seems to only use the maven.compiler.source property.
Doing this in Drools causes very high memory usage (over 5GB) when run
on the SDK, probably because of the high number of asserts.
Log errors and warning after each validator is run, to know
earlier when problems are found.
Move the slowest validator (EFX) to the end to not delay the others.

The complete list of warnings and errors is still logged at the end, as
it was before, to get everyting in one place.
Output validation results earlier (TEDEFO-3685)
We need the bugfixes included in that version.
Use JMH to run the Schematron rules of the SDK being analyzed against
a set of large XML notices, and write the results to a JSON file.
This allows detecting when a change in the rules makes them slower, by
comparing with results from another run.

The notices used in the benchmark are included as resources, as we need
them to be always the same, and to be large enough to make slowdowns
noticeable. So we can't use the notice examples from the SDK being
analyzed.
Add a validation error instead of failing with a NullPointerException.
XmlSchemaValidator: Handle element not found in the schema (TEDEFO-3707)
Add a benchmark for schematron rules
These dependencies are not optional, they are used by all features.
They are included in the full/shaded JAR with all other dependencies
anyways.
It's a dependency of drools-ruleunits-engine, and we don't use anything
from it directly, so we don't need to have it in our pom.
Don't replace the original JAR with the full/shaded JAR, but create
the full JAR with the "-all" suffix.
It's is set to the default value, so we actually don't need to specify
it.
Publish packages to Maven Central
Use a notice with more lots for subtype 16, so that any slowdown is more
noticeable.

Update both notices to SDK 1.13.0, and fix most validation failures.
benchmark: Update notices used in the benchmark
@bertrand-lorentz
Copy link
Contributor Author

Merging without review, as individual changes went through PRs, and this has been tested by checking the current SDK.

@bertrand-lorentz bertrand-lorentz merged commit 3270995 into main Oct 14, 2024
2 checks passed
@bertrand-lorentz bertrand-lorentz deleted the release/1.13.0 branch October 14, 2024 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant