You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2007/02/23 04:46:05 UTC
[jira] Created: (PLUTO-317) Automate version numbers for pluto-site
module
Automate version numbers for pluto-site module
----------------------------------------------
Key: PLUTO-317
URL: https://issues.apache.org/jira/browse/PLUTO-317
Project: Pluto
Issue Type: Improvement
Components: documentation
Affects Versions: 1.1.0
Reporter: Elliot Metsger
Assigned To: Elliot Metsger
Priority: Minor
Fix For: 1.2.0
There are places in the pluto-site module xdoc content where we hardcode the pluto version. Would like to automate this.
Unfortunately the content is not interpolated, so properties have to be injected into the site module, and we have to have a custom site template:
<plugin>
<artifactId>maven-site-plugin</artifactId>
<configuration>
<attributes>
<foo>bar</foo>
</attributes>
<template>site.vm</template>
</configuration>
</plugin>
Right now the maven site mojo does not seem to be reading the <attributes> properly, so I'm scheduling for 1.2.0 since I'm waiting for replies from the maven mailing lists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.