[jira] Updated: (MSITE-533) make site:stage a local file deploy

["Lukas Theussl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSITE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Theussl updated MSITE-533:
--------------------------------

    Component/s: site:stage(-deploy)

> make site:stage a local file deploy
> -----------------------------------
>
>                 Key: MSITE-533
>                 URL: http://jira.codehaus.org/browse/MSITE-533
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Improvement
>          Components: site:deploy, site:stage(-deploy)
>    Affects Versions: 2.2
>            Reporter: Lukas Theussl
>
> As I understand it, site:stage is supposed to be a local preview of site:deploy. However, the site construction is very different in both cases: site:stage changes the <url> pom element of each project and generates the site directly at the target location. Unfortunately, this suffers from a couple of bugs, in particular regarding relative links in multi-module builds, which is potentially confusing for users (and certain developers...) if they find that the staged site is different from the deployed site. site:deploy OTOH generates each site at its own target location and then uses wagen to copy the single sites to the final destination.
> Since site:deploy supports a local file copy, I propose to replace site:stage by such a local deploy. This would make site:stage and deploy equivalent, reduce confusion and maintenance efforts and make site:stage a true preview per definition. Are there any arguments that speak against it?

-- 
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