[jira] Created: (CAMEL-54) move the XSL files to the maven plugin?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-54) move the XSL files to the maven plugin?

JIRA jira@apache.org
move the XSL files to the maven plugin?
---------------------------------------

                 Key: CAMEL-54
                 URL: https://issues.apache.org/activemq/browse/CAMEL-54
             Project: Apache Camel
          Issue Type: Sub-task
            Reporter: James Strachan
            Assignee: Jonas Lim


It'd be great to reuse the html-to-docbook plugin on other projects like ActiveMQ and ServiceMix. While its totally cool being able to overload the XSL's on a per project basis; mostly it seems to be generic apache HTML -> DocBook stuff. So am wondering if it'd make more sense to put these XSL files into the plugin (so that they are shared among all the various projects, rather than cutting and pasting into each project).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-54) move the XSL files to the maven plugin?

JIRA jira@apache.org

     [ https://issues.apache.org/activemq/browse/CAMEL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonas Lim resolved CAMEL-54.
----------------------------

    Resolution: Fixed

fixed in rev: 551512

also added an optional configuration parameter <xslFile>  which will handle an xsl location if a project would like to overload the default  xsl

> move the XSL files to the maven plugin?
> ---------------------------------------
>
>                 Key: CAMEL-54
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-54
>             Project: Apache Camel
>          Issue Type: Sub-task
>            Reporter: James Strachan
>            Assignee: Jonas Lim
>
> It'd be great to reuse the html-to-docbook plugin on other projects like ActiveMQ and ServiceMix. While its totally cool being able to overload the XSL's on a per project basis; mostly it seems to be generic apache HTML -> DocBook stuff. So am wondering if it'd make more sense to put these XSL files into the plugin (so that they are shared among all the various projects, rather than cutting and pasting into each project).

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.