[ http://jira.codehaus.org/browse/DOXIA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267219#action_267219 ]
Data Nucleus commented on DOXIA-104: ------------------------------------ Hi Lukas, i've tried various versions. Most recently 2.1.1 since 2.1 is buggy for validating basic XDOC documents. Yes, it preserves the <meta> in the generated (X)HTML, but I'm not too bothered about preserving them. My question is how do I access them in a velocity file site.vm? ???.head.name or something? Thx > Support use of custom properties in XDOC files > ---------------------------------------------- > > Key: DOXIA-104 > URL: http://jira.codehaus.org/browse/DOXIA-104 > Project: Maven Doxia > Issue Type: Task > Components: Module - Xdoc > Affects Versions: 1.0-alpha-8 > Reporter: Andy Jefferson > Assignee: Lukas Theussl > Priority: Critical > > In the JPOX Maven1 use of "site" we tagged all (XDOC) docs like this > <document> > <properties> > <title>Application Identity</title> > <jpoxpagetype>Persistence</jpoxpagetype> > <jpoxversion>1_2</jpoxversion> > </properties> > ... > </document> > since XDOCs werent validated against any DTD etc. > Then in site.jsl we could access these properties via > <j:set var="jpoxpage_param"> > <x:expr select="./properties/jpoxpagetype"/> > </j:set> > With Maven2 I don't see how I can do this. I define my own skin for JPOX and > in site.vm I have $title, $authors but nothing more. Delving into Doxia I see > where they were set up. No allowance for users own properties. > The requirement for JPOX is that we have a large number of documents, and we > tag each doc for particular categories ... which will then appear on the web > site as horizontal navigation (the default Maven skin only has the navColumn > ... vertical navigation). By being able to tag docs into > categories/subcategories etc we can then generate a site that the user > selects a horizontal nav category, and then a horizontal nav sub-category, > and they see vertical navigation within that subcategory. This was possible > with Maven1 due to the above ability. Without an equivalent in Maven2 we > cannot switch over. > The JPOX docs (from Maven1) are available at > http://www.jpox.org/docs/1_2/index.html > so you can understand what is being talked about here. If you need any more > info let me know. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira