search

DPascalBernard / maven-alfresco-archetypes

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

Relocate the nosnapshot plugin #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The nosnapshot plugin can be taken out of the maven archetypes module 
structure. Its state is quite stable (no real code changes in years), while 
we're releasing it any time we release the archetypes.

As it's referenced in the AMP archetype resources (as a SNAPSHOT!), it would be 
cleaner if we take it out of the main structure and let it follow its own 
release lifecycle.

Original issue reported on code.google.com by carlo.sciolla on 7 Apr 2012 at 2:54

GoogleCodeExporter commented 9 years ago 
Gotcha, I agree. I really hope that the nosnapshot plugin will be soon 
deprecated thanks to the resolution of 
https://issues.alfresco.com/jira/browse/ENH-1232

However, I agree with you that the first step is to detach it from the 
archetype release lifecycle.

I think we can schedule this for the upcoming 4.0 archetype release; I can have 
a look at it this week most likely.

Original comment by mauri...@session.it on 9 Apr 2012 at 11:59

GoogleCodeExporter commented 9 years ago 
This is part of the alfresco-maven-plugin now. It has its own mojo:

https://maven-alfresco-archetypes.googlecode.com/svn/branches/experimental/alfre
sco-lifecycle-aggregator/plugins/alfresco-maven-plugin/src/main/java/org/alfresc
o/maven/plugin/VersionMojo.java

Also I think we could really pull it off a custom plugin, and instead use a 
combination the maven buildhelper:parse-version 
(http://mojo.codehaus.org/build-helper-maven-plugin/parse-version-mojo.html) 
and standard resource filtering.

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