Releases: datasharingframework/dsf-linter
Release 0.1.2
v0.1.2
Bug Fixes
-
Fixed false positive class hierarchy checks for V1 plugins — The linter incorrectly reported that implementation classes did not implement
JavaDelegate, did not extendAbstractServiceDelegate/AbstractTaskMessageSend, or that execution listeners did not implementExecutionListener. This was caused by missing Spring Framework classes in the shaded CLI JAR, which prevented the JVM from resolving plugin class hierarchies at runtime. Spring artifacts (spring-beans,spring-core,spring-jcl) are now explicitly included in the shade configuration. -
Fixed version mismatch between
linter-cliandlinter-core—linter-clireferenced a hardcoded dependency onlinter-core:0.1.0instead of the current project version, causing stale artifacts to be used during the build. The version is now derived from${project.version}.
Upgrade is strongly recommended for all users of v0.1.1.
Contributors:
This release contains contributions from @khalilmalla95.
Release 0.1.1
Summary
Fixed a bug where plugins using DSF Process API v2 were not discovered due to a missing dependency.
Fixes
- API v2 Support: Added
dsf-bpe-process-api-v2to runtime classpath. - Class Loading: Resolved
CLASS_LOADING_FAILEDfor v2 plugins. - Shaded JAR: Included v2 API in the fat JAR for standalone usage.
Contributors:
This release contains contributions from @khalilmalla95.
0.1.0 - First Release
Initial Beta Release
We are excited to announce the first release of DSF Linter - a comprehensive static analysis tool for validating DSF (Data Sharing Framework) process plugins before deployment.
Overview
DSF Linter is a command-line tool that validates BPMN processes, FHIR resources, and plugin configurations from JAR files. It helps developers ensure their DSF process plugins meet quality standards and comply with DSF conventions before deployment.
For more information, visit the DSF Linter Tool documentation.
Thank you for using DSF Linter! We hope it helps you build better DSF process plugins.
This release contains contributions from @khalilmalla95