So if understand well, these encoding variables are just >>needed<< all the times!!
Why not treat XML as XML ? Hence use the encoding header decently.
This is just a shame!
(or I'm mistaking)
This could be a reason I had so many atrocities about encodings in my organization for example...
The funky thing is that such all xdoc and navigation.xml get processed through jelly anyways later (hence as XML), does it mean there's some velocity before ? I don't understand this.
Paul
On Jeudi, nove 20, 2003, at 03:39 Europe/Paris, O'Fallon, Paul (MAN-Corporate) wrote:
My experience has been that navigation.xml is run through velocity in a
multiproject build (actually in the multiproject plugin), but not when
simply running "maven site". It would be great to have navigation.xml run
through velocity in both cases (for consistency's sake -- I pulled my hair
out wondering why one navigation.xml was evaluating velocity tags and
another one wasn't... :-)
- Paul
-----Original Message----- From: Jeffrey Bonevich [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:13 PM To: Maven Users List Subject: Variable substitution in xdocs
I want to refer to pom specific values in my navigation.xml file (i.e. current version, etc.). Can I do variable substitution in xdoc plugin? Since it is velocity based I assume so, but I can find no documentation that tells me what variables I can refer to. ${pom} and ${reactorProject} do not seem to be among them. I have seen one example that used a velocity forEach loop and refers to the variable $reactorProjects. This was in the context of a multi-project; involved setting an attribute on maven:reactor (postprocessing=true). I suspect maybe I can break in here with maven.xml and add my own variables to reference in my xdocs, but thought I would ask before rolling my own.
What ever anyone can feed me, I will be happy to compile and put on the wiki.
jeff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
