From 573a8ee34cc90df235a636d0d7cc59bf95a6a083 Mon Sep 17 00:00:00 2001
From: mindthegab <gabriele@apache.org>
Date: Thu, 10 Jul 2008 09:11:02 +0000
Subject: [PATCH] -- added site deployment properties

git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk/maven-alfresco-archetypes/maven-alfresco-amp-archetype@32 04253f4f-3451-0410-a141-5562f1e59037
---
 pom.xml           | 67 +++++++++++++++++++++++++++++------------------
 src/site/site.xml |  1 -
 2 files changed, 42 insertions(+), 26 deletions(-)

diff --git a/pom.xml b/pom.xml
index 26f1bdd0..9c6b5971 100644
--- a/pom.xml
+++ b/pom.xml
@@ -17,32 +17,49 @@
 	
 -->
 <project>
-  <modelVersion>4.0.0</modelVersion>
-  <groupId>com.sourcesense.alfresco</groupId>
-  <artifactId>maven-alfresco-amp-archetype</artifactId>
-  <packaging>maven-archetype</packaging>
-  <name>Maven Alfresco Amp Archetype</name>
-  <version>1.0.0-SNAPSHOT</version>
-  <description>
-		This archetype aims to provide a standardized approach to development, 
-		release and deployment of Alfresco AMPs (as opposed to Alfresco extensions, released as a different artifact ). 
-		Using standard m2 lifecycle commands (mvn compile package deploy) and generally available plugins (cargo, release, assembly) 
-		we are able to cover a very high percentage of Alfresco lifecycle common use cases. 
-		You are able within minutes to have a compatible AMP module built and its lifecycle supported by Maven, in a fully 
-		transparent way also with open source available AMPs.
-  </description>
-  <parent>
+	<modelVersion>4.0.0</modelVersion>
+	<groupId>com.sourcesense.alfresco</groupId>
+	<artifactId>maven-alfresco-amp-archetype</artifactId>
+	<packaging>maven-archetype</packaging>
+	<name>Maven Alfresco Amp Archetype</name>
+	<version>1.0.0-SNAPSHOT</version>
+	<description>
+		This archetype aims to provide a standardized approach to development, release and deployment of Alfresco AMPs (as opposed to Alfresco
+		extensions, released as a different artifact ). Using standard m2 lifecycle commands (mvn compile package deploy) and generally available
+		plugins (cargo, release, assembly) we are able to cover a very high percentage of Alfresco lifecycle common use cases. You are able within
+		minutes to have a compatible AMP module built and its lifecycle supported by Maven, in a fully transparent way also with open source available
+		AMPs.
+	</description>
+	<properties>
+		<svn.url>${svn.base.url}/trunk/maven-alfresco-archetypes/${artifactId}</svn.url>
+		<site.url>https://repository.sourcesense.com/maven2-sites/maven-alfresco-archetypes/${pom.artifactId}</site.url>
+	</properties>
+	<scm>
+		<developerConnection>scm:svn:${svn.url}</developerConnection>
+		<url>${svn.url}</url>
+	</scm>
+	<parent>
 		<groupId>com.sourcesense.alfresco</groupId>
 		<artifactId>maven-alfresco-archetypes</artifactId>
 		<version>1.0-SNAPSHOT</version>
-  </parent>
-  <build>
-    <extensions>
-      <extension>
-        <groupId>org.apache.maven.archetype</groupId>
-        <artifactId>archetype-packaging</artifactId>
-        <version>2.0-alpha-3</version>
-      </extension>
-    </extensions>
-  </build>
+	</parent>
+	<build>
+		<extensions>
+			<extension>
+				<groupId>org.apache.maven.archetype</groupId>
+				<artifactId>archetype-packaging</artifactId>
+				<version>2.0-alpha-3</version>
+			</extension>
+		</extensions>
+	</build>
+	<distributionManagement>
+		<repository>
+			<id>ss-public</id>
+			<url>scp://repository.sourcesense.com/var/www/demo.sourcesense.com/maven2</url>
+		</repository>
+		<site>
+			<id>ss-site-public</id>
+			<url>scp://repository.sourcesense.com/var/www/demo.sourcesense.com/maven2-sites/${pom.artifactId}</url>
+		</site>
+	</distributionManagement>
 </project>
\ No newline at end of file
diff --git a/src/site/site.xml b/src/site/site.xml
index 700eb065..6e826fbd 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -27,7 +27,6 @@
       <item name="Roadmap" href="http://forge.alfresco.com/docman/view.php/90/1645/ROADMAP.txt"/>
 	  <item name="FAQ" href="faq.html"/>
     </menu>
-    <menu ref="reports"/>
 
   </body>
 </project>