Closed GoogleCodeExporter closed 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
Scheduled for post 1.0.
Original comment by colum...@gmail.com
on 29 Oct 2012 at 11:45
Original comment by colum...@gmail.com
on 14 Feb 2013 at 10:15
Original comment by colum...@gmail.com
on 13 Jun 2013 at 3:28
Issue 65 has been merged into this issue.
Original comment by maurizio...@alfresco.com
on 3 Jul 2014 at 9:41
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
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
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
Original issue reported on code.google.com by
rgau...@gmail.com
on 28 Feb 2012 at 1:31