search

DPascalBernard / maven-alfresco-archetypes

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

Documentation/Comments Should Contain Warning About SCM and 3 Segment Version #69

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create an AMP and set version in pom.xml to 0.1
2. Package and deploy SCM revision 2345 of AMP to WAR (module.version is 
0.1.2345)
3. Make minor changes to AMP source and set version in pom.xml to 0.1.1
4. Package and deploy SCM revision 2356 of AMP to WAR using MMT (module.version 
is 0.1.1.2356)

As far as the AMP stuff is concerned 0.1.2345 is greater than 0.1.1.2356 and 
rightfully so.

There should be a warning in the documentation and comments to account for this 
in one's versioning scheme of the AMP.

Original issue reported on code.google.com by rgau...@gmail.com on 28 Feb 2012 at 1:31

GoogleCodeExporter commented 8 years ago 
Added issue to Alfresco JIRA, please vote ;-) 
https://issues.alfresco.com/jira/browse/ENH-1232

As a work-around, I might suggest to enforce (maybe using the enforcer-plugin?) 
the version to a fixed number of segments, e.g. 0.1.0.2345 and 0.1.1.2356.

Original comment by mauri...@session.it on 6 Apr 2012 at 11:17

GoogleCodeExporter commented 8 years ago 
Scheduled for post 1.0.

Original comment by colum...@gmail.com on 29 Oct 2012 at 11:45

GoogleCodeExporter commented 8 years ago

Original comment by colum...@gmail.com on 14 Feb 2013 at 10:15

GoogleCodeExporter commented 8 years ago

Original comment by colum...@gmail.com on 13 Jun 2013 at 3:28

GoogleCodeExporter commented 8 years ago 
Issue 65 has been merged into this issue.

Original comment by maurizio...@alfresco.com on 3 Jul 2014 at 9:41

GoogleCodeExporter commented 8 years ago 
The only way to avoid this issue (based on the current MMT code) is to avoid to 
use the same Alfresco instance to install SNAPSHOT and non-SNAPSHOT AMP files 
(if you have to, keep 2 different Alfresco instances)

This way, you'll be able to define as many (but up to 4) version segments you 
want/need during the development of your application, release (non-SNAPSHOT) 
and deploy (SNAPSHOT) AMP artifacts into a Maven Repository and fetch them 
later in time to be installed into pre-existing Alfresco environments.

I we agree with this approach, we can ask Documentation to add this warning 
into docs.alfresco.com

Original comment by maurizio...@alfresco.com on 3 Jul 2014 at 10:34

GoogleCodeExporter commented 8 years ago 
An additional enforcement to this behaviour is to:
1. introduce a boolean configuration property in alfresco-maven-plugin called 
"safeSnapshot" (dont really like this name, please help me finding a better one)
2. if safeSnapshot is true, noSnapshot version will
  2.1 decrease the last version segment of 1
  2.2 attach the timestamp as last segment (as it's done right now)
  2.3 attach the suffix "(SNAPSHOT)" to module.description in module.properties file

Original comment by maurizio...@alfresco.com on 3 Jul 2014 at 12:44

GoogleCodeExporter commented 8 years ago 
This issue duplicates issuen #184, so closing this and we'll address this in 
the other issue.

Original comment by colum...@gmail.com on 17 Jul 2014 at 1:22