Claudenw commented on PR #568: URL: https://github.com/apache/creadur-rat/pull/568#issuecomment-3476438111
If Gradle needs an HTML report (as does Maven Report plugin) then perhaps following the anticipated Maven pattern may make sense. My plan to fix Maven is to have the "check" part of the plugin write an XML file into the target space somewhere. Then the "report" part of the plugin will read that XML and generate a report from it. There is also a request to generate multiple reports on a single CLI run. So I expect that the output-style will change to allow multiple style sheets. Not sure how exactly but we can work through that. My point here is that the gradle plugin could generate an XML output in some directory and do this by setting the current output-file setting. Then run one or more XSLT on that. Alternatively, if you would normally generate the output in one go, then create an XSLT that produces what you want and we can see about adding it as a named XSLT. On the question of monolith I am moving toward the UI as a separate package. If each of the UIs is a separate package then we can strip the core down to the minimum necessary to support all the standard CLI options, and put the reporters in separate jars bundled with core and tools. So `apache-rat-<version>.jar` is the CLI version `apache-rat-maven-<version>-<mavenversion>.jar` is the maven plugin version that requires `<mavenversion>` of maven. `apache-rat-ant-<version>-<antversion>.jar` is the ant component version that requires `<antversion>` of Ant. `apache-rat-gradle-<version>-<gradleversion>.jar` is the gradle component version that requires the `<gradleversion>` of Gradle. `apache-rat-core-<version>.jar` is the core component used by and embedded in all the UI versions. The current `tools` component gets broken up and distributed so that all the common bits are in `core` and all the UI specific bits are in the UI plugins. This will pose a problem for documentation generation but I think it will be minor and we can overcome it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
