You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One way to avoid having to implement a ton of one-off annotations or parameters could be to add the ability to specify a post-process XSLT document. This way if someone wants to add/remove/modify certain elements of the resulting docs, they can do so.
This would essentially be the catch-all but care should be taken to to rely on it too heavily instead of providing first-class support for common use cases.
(although there may already be a maven plugin somewhere that could pickup this step... need to research)
The text was updated successfully, but these errors were encountered:
I've heard that request before, and it's not on my todo list, simply for lack of time and the fact that I avoid XSLT like the plague. If you want to contribute it then you're welcome you will make some people happy, as long as the HTML generator which exists now doesn't have to use that ;)
One way to avoid having to implement a ton of one-off annotations or parameters could be to add the ability to specify a post-process XSLT document. This way if someone wants to add/remove/modify certain elements of the resulting docs, they can do so.
This would essentially be the catch-all but care should be taken to to rely on it too heavily instead of providing first-class support for common use cases.
(although there may already be a maven plugin somewhere that could pickup this step... need to research)
The text was updated successfully, but these errors were encountered: