[
http://issues.apache.org/jira/browse/FOR-514?page=comments#action_12312729 ]
Cyriaque Dupoirieux commented on FOR-514:
-----------------------------------------
Answers to Juan Jose :
1) The patch already updates the common-elems-v10.mod file :
Index: main/webapp/resources/schema/dtd/common-elems-v10.mod
===================================================================
--- main/webapp/resources/schema/dtd/common-elems-v10.mod (revision
179778)
+++ main/webapp/resources/schema/dtd/common-elems-v10.mod (working copy)
@@ -61,7 +61,7 @@
<!ATTLIST action %common.att;
dev IDREF #REQUIRED
type (%types;) #IMPLIED
- context (%contexts;) #IMPLIED
+ context CDATA #IMPLIED
importance (%importances;) "medium"
due-to CDATA #IMPLIED
due-to-email CDATA #IMPLIED
It's nice you think about the no more used contexts entity, I forgot it...
2) For context, I want to stay open, that's why I used CDATA and not IDREF. But
I'm Ok for IDREF...
3) The patch already updates all the status.xml I've found adding the following
lines :
<!-- Define here the Title of the Context you want to display in the Changes
pages.
id = the context value of actions
title = Title of the Context
-->
<actionContexts>
<context id="code" title="Changes to the Code Base"/>
<context id="docs" title="Changes to Documentation"/>
<context id="admin" title="Changes to Project Administration"/>
<context id="design" title="Changes to Design"/>
<context id="build" title="Changes to Build"/>
</actionContexts>
> Do not limit status.xml contexts in project info plugin
> -------------------------------------------------------
>
> Key: FOR-514
> URL: http://issues.apache.org/jira/browse/FOR-514
> Project: Forrest
> Type: Improvement
> Components: Plugin: projectInfo
> Reporter: Ross Gardler
> Priority: Minor
> Attachments: 514-patch.txt
>
> (This comment brought over from FOR-487)
> This improvement of changes page is nice.
> I have my own version based on xsl:key definition in order to be able to
> simply manage as many contexts as you can define (My Dtd is not limited to
> "build|docs|code|admin|design".
> The advantage - on my opinion - is that my own contexts are very various and
> not developpement oriented nor language dependant.
> here a short example - using releaseNote... :
> http://cyriaque.dupoirieux.free.fr/changes_6.2.1.html
> The following code replace the 5 blocks <xsl:if test="[EMAIL
> PROTECTED]'build']"> :
> <title>Version <xsl:value-of select="@version"/> (<xsl:value-of
> select="@date"/>)</title>
> + <xsl:for-each
> select="action[generate-id()=generate-id(key('contextes',concat(../@version,
> '_', @context)))]">
> + <xsl:sort select="@context"/>
> + <section>
> + <title><xsl:value-of select="@context"/></title>
> + <ul>
> + <xsl:apply-templates select="key('contextes',concat(../@version, '_',
> @context) )">
> + <xsl:sort select="@type"/>
> + </xsl:apply-templates>
> + </ul>
> + </section>
> + </xsl:for-each>
> Hope you'll like the idea...
> Regards,
> Cyriaque,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
