search

DPascalBernard / maven-alfresco-archetypes

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

AMP archetype should depend on a common base to facilitate upgrades #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The current pom.xml provided by the AMP archetype is intimidating for new
users because it is so large. Also, improvements to the pom have to be
manually added to existing modules.

Atlassian archetypes use a base pom with all the common functionality
resulting in a much smaller project pom for end users.
http://confluence.atlassian.com/display/DEVNET/Atlassian+Plugin+Archetypes

I'm going to look at splitting the amp archetype pom into a base pom in the
same way that atlassian do. I'll do this in a branch.

Original issue reported on code.google.com by damonr...@gmail.com on 16 Sep 2008 at 4:08

GoogleCodeExporter commented 9 years ago 
I completely agree on this one.
I'm about to work on the archetypes until Sunday, shall we align on this one? 
Are you
already working on the code?

Original comment by colum...@gmail.com on 21 Jan 2009 at 12:54

GoogleCodeExporter commented 9 years ago 
Hey Gabrielle,

I started doing some work on this when I opened the issue but got bogged down 
so 
don't think I have anything useful to contribute so far. :-( 

As I mentioned though you might like to check out how atlassian have done this 
though 
cause they have nice ancestor/descendant poms.. See link above.

Damon.

Original comment by damonr...@gmail.com on 21 Jan 2009 at 11:25

GoogleCodeExporter commented 9 years ago 
There's work ongoing for this in the 3.x branches, using maven-calm as common 
super POM.

Will merge this into trunk soon and then close the issue

Original comment by colum...@gmail.com on 4 Dec 2009 at 2:04

GoogleCodeExporter commented 9 years ago

Original comment by colum...@gmail.com on 4 Aug 2011 at 1:35

GoogleCodeExporter commented 9 years ago

Original comment by colum...@gmail.com on 4 Aug 2011 at 1:35

GoogleCodeExporter commented 9 years ago 
I have contributed my personal view on how to define parent POM files that can
1. generalize the build metadata, mostly versions, but also dependency scope 
and very generic plugin configuration - see 
http://maven-alfresco-archetypes.googlecode.com/svn/branches/experimental/quicks
tart-share-runner/poms/alfresco-integration-parent/pom.xml
2. generalize the build behaviour - regardless the final package to produce, 
see 
http://maven-alfresco-archetypes.googlecode.com/svn/branches/experimental/quicks
tart-share-runner/poms/alfresco-web-integration-parent/pom.xml
3. simplify the archetype-generated Maven logic; every pom.xml is lower than 50 
lines long - see 
http://maven-alfresco-archetypes.googlecode.com/svn/branches/experimental/quicks
tart-share-runner/alfresco/pom.xml
4. support different multi-project Maven layouts

Original comment by mauri...@session.it on 18 Apr 2012 at 9:32

GoogleCodeExporter commented 9 years ago 
This is fixed in the Maven Alfresco SDK 1.0.0 release that is going out this 
week. 

In fact it contains a parent POM (alfresco-sdk-parent) that provides all the 
commonalities / lifecycle support through inheritance.

Closing this and setting the Milestone-Release-sdk-1.0.0 fix version.

Original comment by colum...@gmail.com on 29 Oct 2012 at 9:47