inteligr8/alfresco-sdk
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-sdk.git synced 2025-08-07 17:49:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

See project issue 4. Use the buildNumber plugin rather than pom.version for the AMP module version because pom.version may contain alpha characters or -SNAPSHOT. Still need to use properties for the <scm/> tags.

Browse Source 
git-svn-id: http://maven-alfresco-archetypes.googlecode.com/svn/trunk@72 04253f4f-3451-0410-a141-5562f1e59037
This commit is contained in:
damonrand
2008-07-29 14:03:20 +00:00
parent f22267f31a
commit 4770257e5b
2 changed files with 257 additions and 235 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
maven-alfresco-archetypes/maven-alfresco-amp-archetype/src/main/resources/archetype-resources/module.properties
View File

@@ -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=${pom.version}
module.version=${buildNumber}
# The following optional properties can be used to prevent the module from being added
# to inappropriate versions of the WAR file.

32
maven-alfresco-archetypes/maven-alfresco-amp-archetype/src/main/resources/archetype-resources/pom.xml
View File

@@ -22,14 +22,13 @@
<artifactId>${artifactId}</artifactId>
<packaging>amp</packaging>
<name>Maven Alfresco AMP Packaging Sample</name>
<!-- No shapshot or beta version, as this is used for filtering module.properties
As in http://wiki.alfresco.com/wiki/Developing_an_Alfresco_Module:
<!-- 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. "
If you want to use (and I do) maven snapshot capabilities than you could
remove the filtering and maintaining versions (pom and module.properties) aligned manually
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>
@@ -118,8 +117,31 @@
</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 -->
<scm>
<connection>scm:svn:http://domain.com/svn/trunk/</connection>
<developerConnection>scm:svn:https://${maven.username}@domain.com/svn/trunk/</developerConnection>
<url>http://domain.com/svn/trunk/</url>
</scm>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
</configuration>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>