[
https://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSITE-234.
-------------------------------
Resolution: Fixed
Assignee: Herve Boutemy
just use ${project.version} in your site.xml
FYI, this is actually used by skins to generate their site with their actual
build result: see [maven-fluido-skin's
site.xml|http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.3.0/src/site/site.xml?view=markup]
for example
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: https://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
> Assignee: Herve Boutemy
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
