[jira] [Commented] (MSITE-761) Enable deployed site folder to be configurable, eg $project.version not just "staging"

["Gordon Pettey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSITE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111321#comment-15111321 ] 

Gordon Pettey commented on MSITE-761:
-------------------------------------

m-site-p documentation says `stagingDirectory`. http://maven.apache.org/plugins/maven-site-plugin/stage-mojo#stagingDirectory

> Enable deployed site folder to be configurable, eg $project.version not just "staging"
> --------------------------------------------------------------------------------------
>
>                 Key: MSITE-761
>                 URL: https://issues.apache.org/jira/browse/MSITE-761
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>          Components: site:stage(-deploy)
>    Affects Versions: 3.4
>            Reporter: Andy Brook
>
> The site deploy, when configured with a pom distributionManagement url zips up the local "staging" (hard-coded within the site plugin?) folder and unpacks it at the given URL.  As the folder I nominated above is the _project_ folder, I want the target folder to be the current $\{project.version} but there doesn't seem a way to make it do that.  As a result, every time I build, I clobber the current version.  I track many branches, and versions, and want to have access to them all.
> I'd like to add site configuration param like:
> {noformat}
> <siteFolder>${project.version}</siteFolder>
> {noformat}
> So that a version 1.2.3 site-deploy ends up as:
> {noformat}
> scp://webserver/var/www/html/product/1.2.3
> {noformat}
> MSITE-617 could possibly do this, however, this is a very specific slice of that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)