[
https://issues.apache.org/jira/browse/DERBY-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897326#action_12897326
]
Rick Hillegas commented on DERBY-4768:
--------------------------------------
An alternative approach might be to give PlanExporter an api which directs it
to dump the default style sheets somewhere. That would save us the trouble of
maintaining redundant template copies in the codeline and having to build them
into demo/tempates at release time. We would still need to document this
facility.
> Create template style sheets for PlanExporter tool and copy those templates
> into demo/templates as part of building a release
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4768
> URL: https://issues.apache.org/jira/browse/DERBY-4768
> Project: Derby
> Issue Type: Improvement
> Components: Build tools, Demos/Scripts, Documentation, Tools
> Reporter: Rick Hillegas
>
> The PlanExporter tool relies on default style sheets which users should be
> able to customize. Derby's model for this kind of customization can be seen
> in how we handle the security policy file:
> o There is a template policy file parked next to the default policy file in
> the codeline. They are pretty much copies of one another.
> o When building a release, we copy the template policy file into
> demo/templates
> o The user documentation explains how to customize the template policy file
> found in demo/templates
> We should do something similar for the PlanExporter's customizable style
> sheets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
