[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97736 ]
Stefano Bagnara commented on MSITE-234: --------------------------------------- Sorry.. the tree has been changed by the JIRA formater | root (1.0-SNAPSHOT) | - maven-skin (1.1-SNAPSHOT) | - module1 (using maven-skin - 1.1-SNAPSHOT) > Maven skin / version as plugin parameters > ----------------------------------------- > > Key: MSITE-234 > URL: http://jira.codehaus.org/browse/MSITE-234 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Affects Versions: 2.0-beta-5 > Reporter: Stefano Bagnara > > 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). > root > |- maven-skin > '- module1 (using maven-skin) > 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira