You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2011/04/04 14:21:24 UTC
[jira] Closed: (MSITE-573) Default stagingRepositoryId should match
site id
[ http://jira.codehaus.org/browse/MSITE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MSITE-573.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-4
2.3
Assignee: Lukas Theussl
Fixed in [r1088584|http://svn.apache.org/viewvc?rev=1088584&view=rev] and [r1088586|http://svn.apache.org/viewvc?rev=1088586&view=rev]
> Default stagingRepositoryId should match site id
> ------------------------------------------------
>
> Key: MSITE-573
> URL: http://jira.codehaus.org/browse/MSITE-573
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Improvement
> Components: site:stage(-deploy)
> Affects Versions: 2.2, 3.0-beta-3
> Reporter: Lukas Theussl
> Assignee: Lukas Theussl
> Fix For: 2.3, 3.0-beta-4
>
>
> Currently the stagingRepositoryId is hard-coded as "stagingSite" which means one can specify only one staging id in one's settings. Usually staging takes place on the same domain as the main site, so the default settings should be the same.
--
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