Hi all, I was trying to use ${pom.properties} and I found it is an ArrayList of Strings in the form "property:elementName:...:". I was thinking it might be useful to have them as Nodes. What do you think? The problem I am facing is that I have quite a few external links in my documentation and I would like to keep them separate from the docs. I first thought of putting them in the project.properties, but some of these links are quite "tied" to the project (actually the project I am talking about is JaxMe) and It would be nice if I could have them in the pom. Also, if I put them in the project.properties I only have access (at least to my knowledge) when not using dots (.) in the key. I was thinking of something like this:

<properties>
<jaxme-jelly-tag-library>http://jakarta.apache.org/commons/jelly/libs/jaxme/index.html</jaxme-jelly-tag-library>
.....
</properties>


and then access them as: ${project.properties.getChild("jaxme-jelly-tag-library")} or something similar.

This way we would (easily) avoid the problem that arised when moving from nagoya in apache. Other suggestions are very welcome.

I would also like to draw attention to bug #MPXDOC-131 which gives direct access to velocity in user-documentation when maven.docs.src.templates=true. I know I can use maven.xml for this but I beleive it is easier to use it this way. There are no side-effects (maven.docs.src.templates defaults to false) and quite a few benefits!

Regards,

Nacho G. Mac Dowell

PD: Does anybody know where I can find org.apache.maven.project.Model? It is now in a separate artifact, but what project? Thanks!


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to