-
Notifications
You must be signed in to change notification settings - Fork 46
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
Modularize Build #309
Comments
This includes all Java code, all resources, and most parts of Groovy code.
Do you like this RfE and our PoC (cf. #310), @gernotstarke / @rdmueller? At least I would then adjust the documentation accordingly and make the PR final. I have already additional ideas to implement a CLI layer on top of the new core module and hope that some of the others will provide a Maven plugin for HSC. |
sounds good to me, no objections at all. Currently I cannot support you, though. |
Awesome! @rdmueller and i had a chat yesterday and we agreed to go that road with docToolchain as well. I already implemented a core component in dtc here and will release a RC soon. Good to see HSC evolves in the same direction because we then have the possibility to integrate the HSC core module decoupled from Gradle, which is nice. For reference: modularize dtc ADR |
Kudos to the TNG/JGiven project - learned a lot from their nice Gradle setup!
This includes all Java code, all resources, and most parts of Groovy code.
Kudos to the TNG/JGiven project - learned a lot from their nice Gradle setup!
Use Slf4j "nop" impl. to avoid warnings during tests. It is overridden by Gradle logging anyways.
Build modularization completed, kudos to @truhroth, @johthor and other contributors during the CyberLand Open Source Camps! |
We seem to need a little bit of documentation for the modularization before we could release it |
and integrate conversion and sanity checking of the README document into the `gradle-plugin` integration test.
First release candidate (rc0) of modularised build was published to Maven Central on 23rd of June 2024. |
As users we would like to make HSC more modular in order to enable integration it with other build tools (e.g., Maven) or even UIs (like a GUI and a CLI tool for HSC).
Note: This is already foreseen in the architecture.
Background
In our contexts we had already the demand to use HTML Sanity Checker in other tool chains, e.g.,
Authors / Proof of Concept
The text was updated successfully, but these errors were encountered: