[jira] Issue Comment Edited: (MSITE-234) Maven skin / version as plugin parameters

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=97736#action_97736 ] 

dennislundberg edited comment on MSITE-234 at 7/20/08 7:38 AM:
----------------------------------------------------------------

Sorry.. the tree has been changed by the JIRA formater
{noformat}
| root (1.0-SNAPSHOT)
| - maven-skin (1.1-SNAPSHOT)
| - module1 (using maven-skin - 1.1-SNAPSHOT)
{noformat}

      was (Author: bago):
    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