Issue/56 prepare linter core for maven central release#76
Merged
khalilmalla95 merged 20 commits intoJun 2, 2026
Merged
Conversation
Bumps [com.fasterxml.jackson.core:jackson-core](https://github.com/FasterXML/jackson-core) from 2.18.0 to 2.18.6. - [Commits](FasterXML/jackson-core@jackson-core-2.18.0...jackson-core-2.18.6) --- updated-dependencies: - dependency-name: com.fasterxml.jackson.core:jackson-core dependency-version: 2.18.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…support resources
… metadata - Refine project groupId and organization details. - Add SCM and developer metadata. - Configure Maven plugins for source, Javadoc, and artifact signing. - Include distribution and release management profiles. - Update dependency declarations for consistency.
…nd testing instructions.
…ons for detailed issue reporting
… dependency group
…builds, and automated deployment.
…dard - Refactored profile structure in the root pom.xml to match the main DSF repository: - Renamed the `release` profile to `publish-to-maven-central` (handling GPG signing and Sonatype deployment). - Introduced a `generate-source-and-javadoc-jars` profile to centrally manage the attachment of source and javadoc artifacts for all deployable modules. - Removed the redundant `<repository>` entry for Maven Central from `<distributionManagement>`, as the `central-publishing-maven-plugin` manages the deployment directly. - Removed `maven-shade-plugin` from `linter-core/pom.xml` to prevent it from being built as a fat JAR. This ensures `linter-core` acts as a clean library and won't cause classpath collisions (e.g., with Spring, Camunda, or HAPI FHIR) when consumed by other projects. - Removed duplicated source and javadoc plugin executions from `linter-core/pom.xml` since they are now inherited from the parent POM.
…ests - Added `jakarta.xml.bind-api` and `jaxb-runtime` to `linter-core/pom.xml`. - JAXB is no longer included in the standard JDK since Java 11. Because the project targets Java 25, these libraries must be provided explicitly. - This resolves a `java.lang.NoClassDefFoundError: jakarta/xml/bind/annotation/XmlElement` that caused the GitHub Actions unit test job to fail during `DsfMultiPluginLinterTest`, as the HAPI FHIR module requires JAXB at runtime.
khalilmalla95
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.