maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Brook (JIRA)" <>
Subject [jira] [Commented] (MSITE-761) Enable deployed site folder to be configurable, eg $project.version not just "staging"
Date Mon, 25 Jan 2016 09:06:39 GMT


Andy Brook commented on MSITE-761:

Ah, I'd misread that, though it was more about web-url location, than file copy location,
I've got things working as expected now, with the following, thanks!

> Enable deployed site folder to be configurable, eg $project.version not just "staging"
> --------------------------------------------------------------------------------------
>                 Key: MSITE-761
>                 URL:
>             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

View raw message