As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
<?xml version="1.0" encoding="UTF-8"?> <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>org.alfresco.maven.plugins.test</groupId> <artifactId>amp-packaging-test</artifactId> <packaging>amp</packaging> <name>Maven Alfresco AMP Packaging Type Test</name> <version>1.0-0</version> <build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> <plugin> <groupId>org.alfresco.maven.plugin</groupId> <artifactId>maven-amp-plugin</artifactId> <extensions>true</extensions> </plugin> </plugins> </build> <dependencies> <!– need to list these as a provided so that Maven doesn't download them and include them in the AMP, they are provided by the Alfresco application –> <dependency> <groupId>alfresco</groupId> <artifactId>repository</artifactId> <version>2.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring</artifactId> <version>2.0.2</version> <scope>provided</scope> </dependency> </dependencies> </project>
Hi,I'm already using maven in a big alfresco project and I created a project on the forge for accomplishing that task (actually with a POM very similar to yours).Maybe you want to join and contribute to:http://forge.alfresco.com/projects/m2alfresco/Shall we merge this two projects? Considering also that:1. At the moment I'm build with plain mvn war:war with an ad-hoc pom and overlaying my extension with the alfresco war (default behaviour for a war artifact with a war dependency)2. we have a mvn assembly draft configuration to produce AMP like structure (it seems you address this step with you plugin)3. I would like to write a maven-alfresco-plugin which basically wraps Module management tool to deploy extensions also to external wars (this can be an extension)4. Write an archetype to generate extensions skeletonsThe fact is:I would like in the end to have alfresco itself modularized with maven (say different artifact per module, e.g. alfresco-repository and alfresco-webclient separata), and in this sense our effort is really important. But we need some validation from Alfresco if this is the way they also envision, in order to have a proper support for this approach (e.g. release of alfresco artifacts on public maven repos, because now i'm building with privately deployed artifacts).I did not have time to look at the plugin code, but maybe it already covers a lot of what we need. Let join our efforts, as soon as I get permission from my customer, I'll post my results and we can merge it.How do you see this?
