Commit f0e85330 authored by mindthegab's avatar mindthegab
Browse files

added maven-alfresco-lifecycle 1.0.0 super pom using maven calm, refactored...

added maven-alfresco-lifecycle 1.0.0 super pom using maven calm, refactored repositories urls and dependencies

git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@209 04253f4f-3451-0410-a141-5562f1e59037
parent ac80da2e
Loading
Loading
Loading
Loading
+2 −35
Original line number Diff line number Diff line
@@ -18,11 +18,9 @@
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<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.5-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
@@ -30,18 +28,11 @@
		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:https://maven-alfresco-archetypes.googlecode.com/svn/trunk/maven-alfresco-archetypes/maven-alfresco-amp-archetype</developerConnection>
		<url>https://maven-alfresco-archetypes.googlecode.com/svn/trunk/maven-alfresco-archetypes/maven-alfresco-amp-archetype</url>
	</scm>
	<url>${project.artifactId}</url>
	<parent>
		<groupId>com.sourcesense.alfresco</groupId>
		<artifactId>maven-alfresco-archetypes</artifactId>
		<version>1.0.5-SNAPSHOT</version>
		<version>1.9.0-SNAPSHOT</version>
	</parent>
	<build>
		<extensions>
@@ -51,29 +42,5 @@
				<version>2.0-alpha-3</version>
			</extension>
		</extensions>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-release-plugin</artifactId>
				<version>2.0-beta-7</version>
				<configuration>
					<!-- useEditMode>true</useEditMode>-->
					<!--  dryRun>true</dryRun-->
					<preparationGoals>clean package</preparationGoals>
					<goals>deploy site:site site:deploy</goals>
					<tagBase>${svn.tags.url}</tagBase>
				</configuration>
			</plugin>
		</plugins>
	</build>
	<distributionManagement>
		<repository>
			<id>ss-public</id>
			<url>scp://repository.sourcesense.com/var/www/repository.sourcesense.com/maven2</url>
		</repository>
		<site>
			<id>ss-public</id>
			<url>scp://repository.sourcesense.com/var/www/repository.sourcesense.com/maven2-sites/${pom.artifactId}</url>
		</site>
	</distributionManagement>
</project>
+1 −1
Original line number Diff line number Diff line
@@ -23,7 +23,7 @@ module.id=${pom.groupId}.${pom.artifactId}
#module.aliases=myModule-123, my-module
module.title=${pom.name}
module.description=${pom.description}
module.version=${buildNumber}
module.version=${noSnapshotVersion}.${buildNumber}

# The following optional properties can be used to prevent the module from being added
# to inappropriate versions of the WAR file.
+173 −115
Original line number Diff line number Diff line
@@ -3,69 +3,83 @@
		Licensed to the Apache Software Foundation (ASF) under one or more
		contributor license agreements. See the NOTICE file distributed with
		this work for additional information regarding copyright ownership.
	The ASF licenses this file to You under the Apache License, Version 2.0
	(the "License"); you may not use this file except in compliance with
	the License.  You may obtain a copy of the License at
	
	http://www.apache.org/licenses/LICENSE-2.0
	
	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,
	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	See the License for the specific language governing permissions and
	limitations under the License.
		The ASF licenses this file to You under the Apache License, Version
		2.0 (the "License"); you may not use this file except in compliance
		with the License. You may obtain a copy of the License at

		http://www.apache.org/licenses/LICENSE-2.0 Unless required by
		applicable law or agreed to in writing, software distributed under the
		License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
		CONDITIONS OF ANY KIND, either express or implied. See the License for
		the specific language governing permissions and limitations under the
		License.
	-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>${groupId}</groupId>
	<artifactId>${artifactId}</artifactId>
	<packaging>amp</packaging>
	<name>Maven Alfresco AMP Packaging Sample</name>
	<!-- An Alfresco version number must be of the form 1.2.3.4. Using 1.0-SNAPSHOT as the AMP version 
	     will create an exception. See http://wiki.alfresco.com/wiki/Developing_an_Alfresco_Module:
	
	"The version number must be made up of numeric values separated by dots. For example '2.1.56' is a valid version number, '2.3.4a' is not. "

  In order to be able to use Maven snapshots we cannot use the <version/> below as the AMP module
  version. Instead we use the buildnumber-maven-plugin. This requires a scm connection.
	<!--
		An Alfresco version number must be of the form 1.2.3.4. Using
		1.0-SNAPSHOT as the AMP version will create an exception. See
		http://wiki.alfresco.com/wiki/Developing_an_Alfresco_Module: "The
		version number must be made up of numeric values separated by dots.
		For example '2.1.56' is a valid version number, '2.3.4a' is not. " In
		order to be able to use Maven snapshots we cannot use the <version/>
		below as the AMP module version. Instead we use the
		buildnumber-maven-plugin. This requires a scm connection.
	-->
	<version>${version}</version>
	<description>Test AMP project</description>
	<repositories>
		<repository>
			<id>ss-public</id>
			<url>http://repository.sourcesense.com/maven2</url>
			<id>ss-public-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public</url>
		</repository>
		<repository>
			<id>ss-public-snapshots-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public-snapshots</url>
		</repository>
	</repositories>
	<pluginRepositories>
		<pluginRepository>
			<id>ss-public</id>
			<url>http://repository.sourcesense.com/maven2</url>
			<url>http://repository.sourcesense.com/nexus/content/groups/public</url>
		</pluginRepository>
		<pluginRepository>
			<id>ss-public-snapshots-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public-snapshots</url>
			<snapshots>
				<enabled>true</enabled>
			</snapshots>
		</pluginRepository>
	</pluginRepositories>
	<properties>
		<!--Default for which src/main/properties/<env>/application.properties is loaded. NB: 
			used only for the 'test' profile (e.g. '-P test' on the mvn commandline)
			jetty run deployment, does not impact AMP behavior which is typically environment independent
		<!--
			Default for which src/main/properties/<env>/application.properties is
			loaded. NB: used only for the 'test' profile (e.g. '-P test' on the
			mvn commandline) jetty run deployment, does not impact AMP behavior
			which is typically environment independent
		-->
		<env>local</env>
		<!-- Webapp used to test/develop locally the AMP -->
		<webapp.name>${artifactId}-webapp</webapp.name>
		<!--
			| 
			| By default the src/test/properties/local/application.properties uses the property "alfresco.data.location" to  specify where
			| alf_data gets created.
			| For local jetty:run deployment default creation dir is under project root folder (as location is specified relatively to run 			
			| dir). Please add alf_data_jetty in svn/cvs ignores in order not to commit that. You can also specified a different (out of the 	
			| sproject) folder
			| by editing the following properties.
			| DB is also configurable here. Of course keep in sync these two values otherwise you'll get integrity errors.
			| 
			| Empty log dir creates file alfresco.log in appserver default dir. You can also specify a meaningful log directory for the server
			| (add a trailing slash, e.g. '/var/log/alfresco/' ) 
			|
			| Jetty embedded run logs by default in target/alfresco.log 
			| | By default the src/test/properties/local/application.properties
			uses the property "alfresco.data.location" to specify where |
			alf_data gets created. | For local jetty:run deployment default
			creation dir is under project root folder (as location is specified
			relatively to run | dir). Please add alf_data_jetty in svn/cvs
			ignores in order not to commit that. You can also specified a
			different (out of the | sproject) folder | by editing the following
			properties. | DB is also configurable here. Of course keep in sync
			these two values otherwise you'll get integrity errors. | | Empty log
			dir creates file alfresco.log in appserver default dir. You can also
			specify a meaningful log directory for the server | (add a trailing
			slash, e.g. '/var/log/alfresco/' ) | | Jetty embedded run logs by
			default in target/alfresco.log
		-->
		<alfresco.data.location>./alf_data_jetty</alfresco.data.location>
		<alfresco.db.name>alf_jetty</alfresco.db.name>
@@ -95,23 +109,23 @@
			<version>2.0</version>
			<scope>provided</scope>
		</dependency>
		<!-- Example Jar dependency:  will be properly packed into the AMP /lib directory 
		<dependency>
			<groupId>rome</groupId>
			<artifactId>opensearch</artifactId>
			<version>0.1</version>
		<!--
			Example Jar dependency: will be properly packed into the AMP /lib
			directory <dependency> <groupId>rome</groupId>
			<artifactId>opensearch</artifactId> <version>0.1</version>
			</dependency>
		-->
		<!-- Example AMP dependency:  will be properly overlayed in the  WAR produced by the integration-test phase in profile 'webapp'
		<dependency>
			<groupId>org.alfresco</groupId>
			<artifactId>recordsmanagement</artifactId>
			<version>2.1.0</version>
			<type>amp</type>
		</dependency>
		<!--
			Example AMP dependency: will be properly overlayed in the WAR
			produced by the integration-test phase in profile 'webapp'
			<dependency> <groupId>org.alfresco</groupId>
			<artifactId>recordsmanagement</artifactId> <version>2.1.0</version>
			<type>amp</type> </dependency>
		-->
		<!-- By default archetype assumes mysql for test webapp. Change src/test/properties/<env>/application.properties
			 FIXME: support in memory db for cleaner and safer test runs
		<!--
			By default archetype assumes mysql for test webapp. Change
			src/test/properties/<env>/application.properties FIXME: support in
			memory db for cleaner and safer test runs
		-->
		<dependency>
			<groupId>mysql</groupId>
@@ -120,7 +134,10 @@
		</dependency>
		<!-- Don't add here amp dependencies as it will break amp packaging -->
	</dependencies>
	<!-- The scm is required for the buildnumber-maven-plugin which is required for AMP version numbering -->
	<!--
		The scm is required for the buildnumber-maven-plugin which is required
		for AMP version numbering
	-->
	<scm>
		<connection>scm:svn:http://domain.com/svn/trunk/</connection>
		<developerConnection>scm:svn:https://${maven.username}@domain.com/svn/trunk/</developerConnection>
@@ -128,6 +145,20 @@
	</scm>
	<build>
		<plugins>
			<plugin>
				<artifactId>maven-nosnapshot-plugin</artifactId>
				<groupId>com.sourcesense.maven</groupId>
				 <version>0.0.5-SNAPSHOT</version>
				<executions>
					<execution>
						<id>default</id>
						<phase>initialize</phase>
						<goals>
							<goal>strip</goal>
						</goals>
					</execution>
				</executions>
			</plugin>
			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>buildnumber-maven-plugin</artifactId>
@@ -145,7 +176,6 @@
					<doUpdate>false</doUpdate>
				</configuration>
			</plugin>

			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<configuration>
@@ -156,29 +186,31 @@
			<plugin>
				<groupId>org.alfresco.maven.plugin</groupId>
				<artifactId>maven-amp-plugin</artifactId>
				<version>2.0.0</version>
				<version>3.0.1-SNAPSHOT</version>
				<extensions>true</extensions>
				<configuration>
					<archive>
						<addMavenDescriptor>false</addMavenDescriptor>
					</archive>
					<overlays>
						<!-- This sample adds records management module in the finally built AMP
						<overlay>
							<groupId>org.org.alfresco</groupId>
						<!--
							This sample adds records management module in the finally built
							AMP <overlay> <groupId>org.org.alfresco</groupId>
							<artifactId>recordsmanagement</artifactId>
							<version>2.1.0</version>
							<type>amp</type>
						</overlay>
							<version>2.1.0</version> <type>amp</type> </overlay>
						-->
						<!-- The current AMP is always last in order to overwrite other modules' modules.properties
						<overlay></overlay>
						<!--
							The current AMP is always last in order to overwrite other
							modules' modules.properties <overlay></overlay>
						-->
					</overlays>
				</configuration>
			</plugin>
		</plugins>
		<!-- Copies and filters resources in build folder so maven-amp-plugin can pick them up  -->
		<!--
			Copies and filters resources in build folder so maven-amp-plugin can
			pick them up
		-->
		<resources>
			<resource>
				<filtering>true</filtering>
@@ -187,8 +219,11 @@
					<exclude>**README-*</exclude>
				</excludes>
			</resource>
			<!-- Copies and filters AMP config in the proper package 'alfresco/module/${groupId}.${artifactId}' so to enforce 
				 full module naming single sourcing from POM properties  -->
			<!--
				Copies and filters AMP config in the proper package
				'alfresco/module/${groupId}.${artifactId}' so to enforce full module
				naming single sourcing from POM properties
			-->
			<resource>
				<filtering>true</filtering>
				<directory>src/main/config</directory>
@@ -200,11 +235,16 @@
		</resources>
	</build>
	<profiles>
		<!-- Profile used to trigger war creation and integration within Jetty embedded -->
		<!--
			Profile used to trigger war creation and integration within Jetty
			embedded
		-->
		<profile>
			<id>webapp</id>
			<build>
				<filters><filter>src/test/properties/${env}/application.properties</filter></filters>
				<filters>
					<filter>src/test/properties/${env}/application.properties</filter>
				</filters>
				<defaultGoal>jetty:run-exploded</defaultGoal>
				<plugins>
					<plugin>
@@ -225,8 +265,11 @@
							</execution>
						</executions>
						<dependencies>
							<!-- This is required to be re-defined explicitly at plugin level as otherwise the 'amp' extension
								unArchiver won't be available to the maven-dependency-plugin  -->
							<!--
								This is required to be re-defined explicitly at plugin level as
								otherwise the 'amp' extension unArchiver won't be available to
								the maven-dependency-plugin
							-->
							<dependency>
								<groupId>org.alfresco.maven.plugin</groupId>
								<artifactId>maven-amp-plugin</artifactId>
@@ -252,7 +295,10 @@
						</executions>
						<configuration>
							<primaryArtifact>false</primaryArtifact>
							<!-- Don't remove the following line otherwise WAR and AMP builds will be done in the same folder, with unexpected results -->
							<!--
								Don't remove the following line otherwise WAR and AMP builds
								will be done in the same folder, with unexpected results
							-->
							<webappDirectory>${build.directory}/${webapp.name}</webappDirectory>
							<archive>
								<addMavenDescriptor>false</addMavenDescriptor>
@@ -280,12 +326,15 @@
							</webResources>
						</configuration>
						<dependencies>
							<!-- This is required to be re-defined explicitly at plugin level as otherwise the 'amp' extension
								unArchiver won't be available to the maven-war-plugin  -->
							<!--
								This is required to be re-defined explicitly at plugin level as
								otherwise the 'amp' extension unArchiver won't be available to
								the maven-war-plugin
							-->
							<dependency>
								<groupId>org.alfresco.maven.plugin</groupId>
								<artifactId>maven-amp-plugin</artifactId>
								<version>2.0.0</version>
								<version>3.0.1-SNAPSHOT</version>
							</dependency>
						</dependencies>
					</plugin>
@@ -315,8 +364,11 @@
						</executions>
					</plugin>
				</plugins>
				<!-- When invoking 'mvn integration-test', the following alf configs are added to the test war in order to be able to run it seamlessly.
					NB: the application.properties file is filtered with alfresco.db.name and alf.data.location POM properties as default configuration
				<!--
					When invoking 'mvn integration-test', the following alf configs are
					added to the test war in order to be able to run it seamlessly. NB:
					the application.properties file is filtered with alfresco.db.name
					and alf.data.location POM properties as default configuration
				-->
				<testResources>
					<testResource>
@@ -329,9 +381,11 @@
						<directory>src/test/properties/${env}</directory>
						<targetPath>alfresco/extension</targetPath>
					</testResource>
					<!-- src/main/config/ is copied into  ==> target/test-classes/alfresco/module/${groupId}.${artifactId} to
						be picked up by the maven-war plugin
						Best practice tacken from recordsmanagement.amp, is enforced troughout the whole archetype. 
					<!--
						src/main/config/ is copied into ==>
						target/test-classes/alfresco/module/${groupId}.${artifactId} to be
						picked up by the maven-war plugin Best practice tacken from
						recordsmanagement.amp, is enforced troughout the whole archetype.
						This convention is also used for module.properties filtering.
					-->
					<testResource>
@@ -344,13 +398,17 @@
					</testResource>
				</testResources>
			</build>
			<!-- Here you can add test dependencies you want to have included in the the WAR (not in the AMP, built in the main profile) 
				|
				| Typical use case: add here additional AMPs that you want to test compatibility of with the current module
				|
			<!--
				Here you can add test dependencies you want to have included in the
				the WAR (not in the AMP, built in the main profile) | | Typical use
				case: add here additional AMPs that you want to test compatibility
				of with the current module |
			-->
			<dependencies>
				<!-- This is the alfresco version you're testing the AMP against. Don't remove if you want jetty to be able to deploy a WAR :) -->
				<!--
					This is the alfresco version you're testing the AMP against. Don't
					remove if you want jetty to be able to deploy a WAR :)
				-->
				<dependency>
					<groupId>org.alfresco</groupId>
					<artifactId>alfresco</artifactId>
+3 −38
Original line number Diff line number Diff line
@@ -18,16 +18,14 @@
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.sourcesense.alfresco</groupId>
	<artifactId>maven-alfresco-extension-archetype</artifactId>
	<version>1.1.5-SNAPSHOT</version>
	<packaging>maven-archetype</packaging>
	<name>Maven alfresco Extension archetype</name>
	<url>${site.url}</url>
	<url>${project.artifactId}</url>
	<parent>
		<groupId>com.sourcesense.alfresco</groupId>
		<artifactId>maven-alfresco-archetypes</artifactId>
		<version>1.0.5-SNAPSHOT</version>
		<version>1.9.0-SNAPSHOT</version>
	</parent>
	<description>
		This archetype developed aims to provide a standardized approach to development, release and deployment of Alfresco extensions (as opposed to
@@ -39,14 +37,6 @@
		least, m2 build is more likely to be maintained and improved (especially in the likely case Alfresco moves to maven2). For more details on the
		m2 apprach please refer instead to README Section (or directly and to README-m2.txt of the generated project).
	</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:https://maven-alfresco-archetypes.googlecode.com/svn/trunk/maven-alfresco-archetypes/maven-alfresco-extension-archetype</developerConnection>
		<url>https://maven-alfresco-archetypes.googlecode.com/svn/trunk/maven-alfresco-archetypes/maven-alfresco-extension-archetype</url>
	</scm>
	<build>
		<extensions>
			<extension>
@@ -57,31 +47,6 @@
			<!-- Unreleased version of webdav wagon plugin which fixes a boring stacktrace logging from this provider. 
				FIXME: Improve the fix and submit the patch 
			-->

		</extensions>	
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-release-plugin</artifactId>
				<version>2.0-beta-7</version>
				<configuration>
					<!-- useEditMode>true</useEditMode>-->
					<!--  dryRun>true</dryRun-->
					<preparationGoals>clean package</preparationGoals>
					<goals>deploy site:site site:deploy</goals>
					<tagBase>${svn.tags.url}</tagBase>
				</configuration>
			</plugin>
		</plugins>
	</build>
	<distributionManagement>
		<repository>
			<id>ss-public</id>
			<url>scp://repository.sourcesense.com/var/www/repository.sourcesense.com/maven2</url>
		</repository>
		<site>
			<id>ss-public</id>
			<url>scp://repository.sourcesense.com/var/www/repository.sourcesense.com/maven2-sites/${pom.artifactId}</url>
		</site>
	</distributionManagement>
</project>
+18 −30
Original line number Diff line number Diff line
@@ -38,12 +38,6 @@
		| -Dwebapp.name=<extensionName> -   name of the WAR artifact to be built (default: ${artifactId}-{version}.jar )
		| -Denterprise   - Includes LDAP configuration as defined in application.properties
	-->
	<repositories>
		<repository>
			<id>ss-public</id>
			<url>http://repository.sourcesense.com/maven2</url>
		</repository>
	</repositories>
	<!-- Default properties -->
	<properties>
		<!-- src/main/properties/<env>/application.properties is loaded -->
@@ -95,25 +89,27 @@
		| Alfresco Community dependencies are generally available in ss-public repo. 
		| FIXME: Alfresco enterprise dependencies are only available on SS repo ATM. Alfresco *needs* to deliver their artifacts on (at least) partner repos
		|-->
	<repositories>
		<repository>
			<id>ss-public-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public</url>
		</repository>
		<repository>
			<id>ss-public-snapshots-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public-snapshots</url>
		</repository>
	</repositories>
	<pluginRepositories>
		<pluginRepository>
			<id>codehaus snapshot repository</id>
			<url>http://snapshots.repository.codehaus.org/</url>
			<releases>
				<enabled>true</enabled>
			</releases>
		</pluginRepository>
		<pluginRepository>
			<id>Maven Snapshots</id>
			<url>http://snapshots.maven.codehaus.org/maven2/</url>
			<snapshots></snapshots>
			<releases>
				<enabled>false</enabled>
			</releases>
			<id>ss-public</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public</url>
		</pluginRepository>
		<pluginRepository>
			<id>ss-public</id>
			<url>http://repository.sourcesense.com/maven2</url>
			<id>ss-public-snapshots-mirror</id>
			<url>http://repository.sourcesense.com/nexus/content/groups/public-snapshots</url>
			<snapshots>
				<enabled>true</enabled>
			</snapshots>
		</pluginRepository>
	</pluginRepositories>
	<!-- Uncomment SCM definitions in order to have mvn release:perform to actually tag the code
@@ -449,14 +445,6 @@
			| Enable this repo in case of non publicly redistributable artifacts (Sourcesense private repositories via webdav)
			|
		-->
		<repository>
			<id>ss-private</id>
			<url>dav:https://dev.sourcesense.com/repos/dev/maven2</url>
		</repository>
		<site>
			<id>ss-site-private</id>
			<url>dav:https://dev.sourcesense.com/cargo/maven2-sites</url>
		</site>
	</distributionManagement>

	<!-- 
Loading