Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-2269

Allow AMPs to include literals in version number (e.g. -SNAPSHOT)

    Details

      Description

      At the moment Alfresco does not allow AMPs to have literals in their version number.

      This makes very complex to manage custom versioning schemes, beta/alfa/RCs, and non linear feature based development.

      An example of this limitation is given in the Maven Alfresco Lifecycle project, as discussed extensively in http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=65 and http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=69 (also because Alfresco does not allow AMPs downgrading).

      MER - Edit so the maven SDK would like to use maven conventions for versions of AMPs.

        Attachments

          Issue Links

            Activity

            Hide
            pmonks Peter Monks [X] (Inactive) added a comment -

            Having MMT use Maven-style version numbers, in their full glory, would be ideal.

            Show
            pmonks Peter Monks [X] (Inactive) added a comment - Having MMT use Maven-style version numbers, in their full glory, would be ideal.
            Hide
            pmonks Peter Monks [X] (Inactive) added a comment -

            Related to this, it should be possible to express module dependencies using Maven-style version number ranges too.

            Show
            pmonks Peter Monks [X] (Inactive) added a comment - Related to this, it should be possible to express module dependencies using Maven-style version number ranges too.
            Hide
            gcolumbro Gabriele Columbro [X] (Inactive) added a comment -

            This is a blocker for https://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=184, i.e. for a "proper" release of the SDK for 5 oh.

            Can we move this to the backlog (and probably also the related ALF-17624) and address it (ideally) for 5 oh?

            This would be a great simplification for developers and a a little bit of pay back for all the Maven SDK releases that we did with the Community

            Show
            gcolumbro Gabriele Columbro [X] (Inactive) added a comment - This is a blocker for https://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=184 , i.e. for a "proper" release of the SDK for 5 oh. Can we move this to the backlog (and probably also the related ALF-17624 ) and address it (ideally) for 5 oh? This would be a great simplification for developers and a a little bit of pay back for all the Maven SDK releases that we did with the Community
            Hide
            gcolumbro Gabriele Columbro [X] (Inactive) added a comment -

            Product management has evaluated the enhancement you requested, and has decided that it fits within the direction of the product.

            As such, it has been placed on the backlog to be implemented in a future release. At this point we have no time frame for when this functionality will be available in the product, but will notify you when a version that includes this has been released.

            Show
            gcolumbro Gabriele Columbro [X] (Inactive) added a comment - Product management has evaluated the enhancement you requested, and has decided that it fits within the direction of the product. As such, it has been placed on the backlog to be implemented in a future release. At this point we have no time frame for when this functionality will be available in the product, but will notify you when a version that includes this has been released.
            Hide
            mrogers Mark Rogers [X] (Inactive) added a comment - - edited

            Maven numbering scheme is http://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#A1000661

            Major.Minor.Incremental-BuildNumber-qualifier
            Where a release with a qualifier is older than one with not.

            Alfresco's numbering scheme is currently
            Major.Minor.Incremental label where label is used for hot fix version, community version or other marketing mandated stuff like the infamous R releases or trial versins. Community versions don't have incremental releases. Maven builds don't have hot fix numbers.

            The minimal change is just add the string "qualifier" and the logic in AMPs to understand it. However we will need to think about hot fix versions since they arn't compatible with maven version numbers. However would we ever mandate a hot fix version in an AMP? If so we can either treat the version as a string or do a special fix. However that "special" is a deviation from how maven works.

            Also do we keep the label field for marketing's use or co-opt it. At the moment its free format however we are potentially going to tie it down with this release. I'm tempted to add another field.

            Show
            mrogers Mark Rogers [X] (Inactive) added a comment - - edited Maven numbering scheme is http://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#A1000661 Major.Minor.Incremental-BuildNumber-qualifier Where a release with a qualifier is older than one with not. Alfresco's numbering scheme is currently Major.Minor.Incremental label where label is used for hot fix version, community version or other marketing mandated stuff like the infamous R releases or trial versins. Community versions don't have incremental releases. Maven builds don't have hot fix numbers. The minimal change is just add the string "qualifier" and the logic in AMPs to understand it. However we will need to think about hot fix versions since they arn't compatible with maven version numbers. However would we ever mandate a hot fix version in an AMP? If so we can either treat the version as a string or do a special fix. However that "special" is a deviation from how maven works. Also do we keep the label field for marketing's use or co-opt it. At the moment its free format however we are potentially going to tie it down with this release. I'm tempted to add another field.
            Hide
            gjames Gethin James added a comment -

            I think its too big a job to change the Alfresco VersionNumber. However, I believe we can create a ModuleVersionNumber class and update the ModuleComponent/MMT. I've done most of the work for this on : https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GETHIN/MODULEVERSION . It would need thorough testing because the VersionNumber is serialized to the registry.

            Show
            gjames Gethin James added a comment - I think its too big a job to change the Alfresco VersionNumber. However, I believe we can create a ModuleVersionNumber class and update the ModuleComponent/MMT. I've done most of the work for this on : https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GETHIN/MODULEVERSION . It would need thorough testing because the VersionNumber is serialized to the registry.

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                gcolumbro Gabriele Columbro [X] (Inactive)
              • Votes:
                3 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: