sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SLING-8104) Avoid magic when merging features
Date Thu, 15 Nov 2018 15:45:00 GMT


ASF GitHub Bot commented on SLING-8104:

bosschaert opened a new pull request #8: SLING-8104 Avoid magic when merging features
   When merging artifacts/bundles, they need to be selected from a provided
   override list if the artifact versions are not the same. The list has
   the following syntax:
   Where <resolution> is one of the following:
     ALL - select all the artifacts
     HIGHEST - select only the artifact with the highest version number
     LATEST - select only the artifact provided latest
     <version> - select this specific version
   When comparing version numbers these are converted to OSGi version
   numbers and the OSGi version number ordering is applied.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Avoid magic when merging features
> ---------------------------------
>                 Key: SLING-8104
>                 URL:
>             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

View raw message