forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] Commented: (FOR-595) Hard-coded project name in input.projectinfo plugin
Date Tue, 18 Apr 2006 12:28:32 GMT
    [ ] 

Gavin commented on FOR-595:

I have an idea that may cure this but not sure of the 'how'.

What about we create a <comment></comment> element that when processed by genericMarkup.ft
, gets converted into
<xsl:comment></xsl:comment>. Then the final output will render correctly into
<!-- --> and will work for both comments and SSI commands.?

So in the theme.fv file we could have :-

<forrest:contract name="genericMarkup">
            <forrest:property name="genericMarkup">
		    <comment>This is a comment</comment>

Then we transform this in genericMarkup.ft :-

 <xsl:template match="/">
            <xsl:copy-of select="$genericMarkup/*"/>

Now somewhere above we get it to check for <comment> and transform it into <xsl:comment>
, this is the bit I'm stuck on.

Then, hopefully the output file will contain <!-- This is a comment -->

For SSI the deal is the same, in the theme.fv file we say :-

<comment>#include virtual="/" </comment>

Which after processing will say:-

<!--#include virtual="/" -->

OR - Is there a way of putting <xsl:comment> directly into the theme.fv file - I tried
it already as is and got :-

The prefix "xsl" for element "xsl:comment" is not bound , hence the above idea.


> Hard-coded project name in input.projectinfo plugin
> ---------------------------------------------------
>          Key: FOR-595
>          URL:
>      Project: Forrest
>         Type: Bug

>   Components: Plugin: input.projectInfo
>     Versions: 0.7
>     Reporter: fuat ormaci

> Title of release notes page always reads 
> Release Notes for Apache Forrest X.Y
> The string "Apache Forrest" should not be hard-coded in releaseNotes2document.xsl, real
project name has to be picked instead.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message