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 2020/04/30 04:44:00 UTC

[jira] [Closed] (SLING-9361) Merge feature and feature.io modules

     [ https://issues.apache.org/jira/browse/SLING-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-9361.
-----------------------------------

> Merge feature and feature.io modules
> ------------------------------------
>
>                 Key: SLING-9361
>                 URL: https://issues.apache.org/jira/browse/SLING-9361
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model 1.2.0
>
>
> As discussed in the mailing list, we should merge the two modules feature and feature.io. From the initial mail:
> We have two bundles which make up the feature model, o.a.s.feature and o.a.s.feature.io - while the first one contains the model, the second one contains reading/writing models in JSON.
> I initially kept them separate to leave it open whether we will use JSON as the serialization format and also to keep the feature model itself free from any additional dependencies. I think by now we have settled on the format and the model now depends on JSON api as well for some features like the extensions.
> I think this separation is today more artifically and does not provide any value. So I would prefer of merging the IO stuff into the feature model and retire feature io as a separate git repository.
> (package names would of course stay the same) 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)