Variable substitution in xdocs?
I would like to use variables, such as pom.currentVersion, in xdocs. Is this possible? I haven't found any docs that says it is and a very cursory look at the code suggests the same. Michael -- Michael Schuerig Failures to use one's frontal lobes mailto:[EMAIL PROTECTED]can result in the loss of them. http://www.schuerig.de/michael/ --William H. Calvin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Variable substitution in xdocs
Have a look at the navigation-aggregate.xml template that's part of
multiproject.
It does something like this:
#foreach ($reactorProject in $reactorProjects)
item name=$reactorProject.name
href=/${aggregateDir}${reactorProject.artifactId}/index.html/
#end
And reactorProject is just a POM.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 21/11/2003 06:02:20 PM:
I have tried setting up a very simple multiproject (a master project and
one subproject) - still no go for $pom or $project. Definetely gets
$reactorProjects in the top level, but not much else I can find in the
subproject. Is there a context at which I can get that could spit out
the names of all variables available to the page when processing?
jeff
[EMAIL PROTECTED] wrote:
From memory the xdocs plugin will look in target/navigation.xml for a
generated file in preference to ${maven.docs.src}/navigation.xml.
multiproject uses this to pre-process the nav file.
You could simply steal the stuff from multiproject.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 20/11/2003 11:12:41 AM:
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Variable substitution in xdocs
dIon -
This works very nicely for the toplevel project (the one from which you
run multiproject) but appears to have no impact on subprojects - cannot
get at anything in those apparently. What I am trying to do is:
* iterate over all the projects at the top level (which can be done as
in navigation-aggregate.xml)
* get at individual pom properties at the subproject level (so I want a
link to the current version of jar file for each subproject w/o having
to hard-code the version in navigation.xml) (this apparently cannot be done)
jeff
[EMAIL PROTECTED] wrote:
Have a look at the navigation-aggregate.xml template that's part of
multiproject.
It does something like this:
#foreach ($reactorProject in $reactorProjects)
item name=$reactorProject.name
href=/${aggregateDir}${reactorProject.artifactId}/index.html/
#end
And reactorProject is just a POM.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 21/11/2003 06:02:20 PM:
I have tried setting up a very simple multiproject (a master project and
one subproject) - still no go for $pom or $project. Definetely gets
$reactorProjects in the top level, but not much else I can find in the
subproject. Is there a context at which I can get that could spit out
the names of all variables available to the page when processing?
jeff
[EMAIL PROTECTED] wrote:
From memory the xdocs plugin will look in target/navigation.xml for a
generated file in preference to ${maven.docs.src}/navigation.xml.
multiproject uses this to pre-process the nav file.
You could simply steal the stuff from multiproject.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 20/11/2003 11:12:41 AM:
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]
-
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]
Re: Variable substitution in xdocs
Are you really meaning it's being run through velocity ??
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]
Re: Variable substitution in xdocs
I have tried setting up a very simple multiproject (a master project and
one subproject) - still no go for $pom or $project. Definetely gets
$reactorProjects in the top level, but not much else I can find in the
subproject. Is there a context at which I can get that could spit out
the names of all variables available to the page when processing?
jeff
[EMAIL PROTECTED] wrote:
From memory the xdocs plugin will look in target/navigation.xml for a
generated file in preference to ${maven.docs.src}/navigation.xml.
multiproject uses this to pre-process the nav file.
You could simply steal the stuff from multiproject.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 20/11/2003 11:12:41 AM:
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]
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]
RE: Variable substitution in xdocs
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]
Re: Variable substitution in xdocs
From memory the xdocs plugin will look in target/navigation.xml for a
generated file in preference to ${maven.docs.src}/navigation.xml.
multiproject uses this to pre-process the nav file.
You could simply steal the stuff from multiproject.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich [EMAIL PROTECTED] wrote on 20/11/2003 11:12:41 AM:
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]
