You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/04/11 00:14:00 UTC
[jira] Created: (MSITE-400) Make repository id for stage-deploy
configurable
Make repository id for stage-deploy configurable
------------------------------------------------
Key: MSITE-400
URL: http://jira.codehaus.org/browse/MSITE-400
Project: Maven 2.x Site Plugin
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Benjamin Bentmann
The {{stage-deploy}} goal is currently hard-coded to use "stagingSite" as the repository id. For deployments to secured servers, users need to provide a corresponding server entry in the {{settings.xml}}. While the hard-coded id "stagingSite" alone is already obscure, this doesn't scale when one needs to stage sites to different servers with different credentials.
--
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
[jira] Closed: (MSITE-400) Make repository id for stage-deploy
configurable
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MSITE-400.
-----------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0.1
Done in [r764090|http://svn.eu.apache.org/viewvc?view=rev&revision=764090].
> Make repository id for stage-deploy configurable
> ------------------------------------------------
>
> Key: MSITE-400
> URL: http://jira.codehaus.org/browse/MSITE-400
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 2.0.1
>
>
> The {{stage-deploy}} goal is currently hard-coded to use "stagingSite" as the repository id. For deployments to secured servers, users need to provide a corresponding server entry in the {{settings.xml}}. While the hard-coded id "stagingSite" alone is already obscure, this doesn't scale when one needs to stage sites to different servers with different credentials.
--
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