[jira] [Closed] (PLUTO-317) Automate version numbers for pluto-site module

"Scott Nicklous (JIRA)" <[email protected]>
Newsgroups gmane.comp.jakarta.pluto.devel
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/PLUTO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Nicklous closed PLUTO-317.
--------------------------------
    Resolution: Fixed

please retest with v3

> 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
>            Assignee: Elliot Metsger
>            Priority: Minor
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.