[forge-issues] [JBoss JIRA] (FORGE-988) Refactor AddonManager to support addon version conflicts

[George Gastaldi (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi updated FORGE-988:
----------------------------------

    Fix Version/s: 2.0.0.Alpha9
                       (was: 2.0.0.Alpha8)

    
> Refactor AddonManager to support addon version conflicts
> --------------------------------------------------------
>
>                 Key: FORGE-988
>                 URL: https://issues.jboss.org/browse/FORGE-988
>             Project: Forge
>          Issue Type: Enhancement
>          Components: Addon Manager
>    Affects Versions: 2.0.0.Alpha6
>            Reporter: George Gastaldi
>            Assignee: George Gastaldi
>            Priority: Critical
>             Fix For: 2.0.0.Alpha9
>
>
> Given that Addons A(1.0), B (1.0), C(1.0)  are installed in an AddonRepository, and C(1.0) depends on B(1.0), when an addon D(1.0) to be installed requires B(1.1), there should be a way to warn against incompatibilities and let the user decide what to do. Same when D(1.0) depends on B(2.0)
> Basically an addon version is composed of Major.Minor.Micro
> In relation to the installed addon version and the requested addon version the following rules should be followed: 
> - When Major version is different, the addons are assumed be completely incompatible (even if in practice that is not true). Fail installation
> - When Minor version is different, compatibility may be assured only if the requested version is less or equal to the required version. Prompt for installation of necessary version.
> - When Micro version is different, the addon is totally compatible, thus no  compatibility check is required. No problem to install

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira