You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/11/15 06:44:00 UTC
[jira] [Updated] (SLING-8104) Avoid magic when merging features
[ https://issues.apache.org/jira/browse/SLING-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-8104:
------------------------------------
Description:
Currently when features are merged a simple algorithm is applied which just picks the highest version based on the artifact version. However this version might not have no meaning at all and might not really reflect what has changed inside the bundle.
Especially when there is a major version change, this approach seems to be clearly wrong
But in the end, picking a single version is magic.
While the problem could probably be solved by using something like a resolver and figure out if just one version is enough or if both versions are needed, without a resolver there is no way to figure this out.
Therefore we should provide a similar way as we do for variables at the moment: if there is a clash the caller needs to provide context on what to choose.
was:
Currently when features are merged a simple algorithm is applied which just picks the highest version based on the bundle version. However this version might not have no meaning at all and might not really reflect what has changed inside the bundle.
Especially when there is a major version change, this approach seems to be clearly wrong
But in the end, picking a single version is magic.
While the problem could probably be solved by using something like a resolver and figure out if just one version is enough or if both versions are needed, without a resolver there is no way to figure this out.
Therefore we should provide a similar way as we do for variables at the moment: if there is a clash the caller needs to provide context on what to choose.
> Avoid magic when merging features
> ---------------------------------
>
> Key: SLING-8104
> URL: https://issues.apache.org/jira/browse/SLING-8104
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: David Bosschaert
> Priority: Blocker
> Fix For: slingfeature-maven-plugin 1.0.0, Feature Model 0.2.2
>
>
> Currently when features are merged a simple algorithm is applied which just picks the highest version based on the artifact version. However this version might not have no meaning at all and might not really reflect what has changed inside the bundle.
> Especially when there is a major version change, this approach seems to be clearly wrong
> But in the end, picking a single version is magic.
> While the problem could probably be solved by using something like a resolver and figure out if just one version is enough or if both versions are needed, without a resolver there is no way to figure this out.
> Therefore we should provide a similar way as we do for variables at the moment: if there is a clash the caller needs to provide context on what to choose.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)