Author: bentmann
Date: Fri Apr 10 22:42:19 2009
New Revision: 764090

URL: http://svn.apache.org/viewvc?rev=764090&view=rev
Log:
[MSITE-400] Make repository id for stage-deploy configurable

Modified:
    
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/SiteStageDeployMojo.java

Modified: 
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/SiteStageDeployMojo.java
URL: 
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/SiteStageDeployMojo.java?rev=764090&r1=764089&r2=764090&view=diff
==============================================================================
--- 
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/SiteStageDeployMojo.java
 (original)
+++ 
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/SiteStageDeployMojo.java
 Fri Apr 10 22:42:19 2009
@@ -74,6 +74,16 @@
     private String stagingSiteURL;
/**
+     * The identifier of the repository where the staging site will be 
deployed. This id will be used to lookup a
+     * corresponding <code>&lt;server&gt;</code> entry from the 
<code>settings.xml</code>. If a matching
+     * <code>&lt;server&gt;</code> entry is found, its configured credentials 
will be used for authentication.
+ * + * @parameter expression="${stagingRepositoryId}" default-value="stagingSite"
+     * @since 2.0.1
+     */
+    private String stagingRepositoryId;

I would have liked to bump the plugin version to 2.1 due to this feature addition but noticed there is already a bucket for 2.1 in JIRA (targetting Doxia 1.1). So I wasn't sure whether the 2.0.1 version should just be dropped and its issues merged into the 2.1 bucket or whether 2.0.1 should be renamed to 2.1 and 2.1 to 2.2. Given Dennis is doing most of the work on the Site Plugin, I'm leaving the proper versioning to his judgement.


Benjamin


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to