search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Document mmt-maven-plugin default Alfresco version used and how to override #90

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Following up conversation on the list - 
https://groups.google.com/forum/?fromgroups#!topic/maven-alfresco/YBCN4QK4qvo

Write documentation based on mmt-maven-plugin dependency on alfresco-core; by 
default the version in use is the last Community one (4.0.d), however some 
users might want to override it using the standard Maven mechanism - 
http://www.sonatype.com/people/2008/04/how-to-override-a-plugins-dependency-in-m
aven/

Original issue reported on code.google.com by mauri...@session.it on 14 Jun 2012 at 12:03

GoogleCodeExporter commented 9 years ago 
Please create Wiki page (on wiki.alfresco.com) and drop this info

Original comment by mauri...@session.it on 14 Jun 2012 at 12:06

GoogleCodeExporter commented 9 years ago 
In my opinion, mmt plugin should use the same alfresco version. Otherwise, you 
can have some issue if you use alfresco mmt 4.0.D to install an AMP in alfresco 
3.1.

Original comment by alexis.t...@gmail.com on 14 Jun 2012 at 12:15

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Alfresco MMT *should be* backward-compatible; the current mmt-maven-plugin, 
although not using the same version, has been successfully tested on Alfresco 
Enterprise 3.4.x

Unfortunately Maven does not allow (as far as I know) to specify a plugin 
dependency coordinate (version, groupId) as a standard plugin's configuration 
(i.e. placing a placeholder ${alfresco.version} in mmt-maven-plugin/pom.xml), 
therefore the MMT plugin *needs* to specify a default, but the end user can 
always override it and use the one of his choice.

The archetypes and Platform / Developer POM files will of course force the 
mmt-plugin configuration, forcing the ${alfresco.version} used in the current 
build.

Original comment by mauri...@session.it on 14 Jun 2012 at 12:28

GoogleCodeExporter commented 9 years ago 
I think we are pretty close to close this one, also because now 
alfresco-maven-plugin only depends on alfresco-mmt.

A possible solution would be: 

- alfresco-maven-plugin sets a fixed version
- in the alfresco-sdk-parent we add an override of the version, with a 
placeholder for overriding the dependency in the plugin section

WDYT?

Original comment by colum...@gmail.com on 30 Oct 2012 at 12:18

GoogleCodeExporter commented 9 years ago 
Documented at:

https://artifacts.alfresco.com/nexus/content/repositories/alfresco-docs/alfresco
-lifecycle-aggregator/latest/plugins/alfresco-maven-plugin/index.html

Original comment by colum...@gmail.com on 4 Nov 2012 at 11:56