[
https://issues.apache.org/jira/browse/MSITE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Brook updated MSITE-761:
-----------------------------
Description:
The site deploy, when configured with a pom distributionManagement url zips up
the local 'staging' 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.
Id like to add site configuration param like:
{noformat}
<siteFolder>${project.version}</siteFolder>
{noformat}
Relates to MSITE-716, possibly a dupe from one view
was:
The site deploy, when configured with a pom distributionManagement url zips up
the local 'staging' 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.
Id like to add site configuration param like:
{noformat}
<siteFolder>${project.version}</siteFolder>
{noformat}
Relates to MSITE-716, possibly a dupe from one view
> 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' 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.
> Id like to add site configuration param like:
> {noformat}
> <siteFolder>${project.version}</siteFolder>
> {noformat}
> Relates to MSITE-716, possibly a dupe from one view
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
