I merged the two repositories, so from now one o.a.s.feature contains
both modules and o.a.s.feature.io is deprecated
So whenever you update to the (upcoming) 1.2.0 release of o.a.s.feature,
make sure to remove the depedency to o.a.s.feature.io
Regards
Carsten
On 26.03.2020 18:14, Carsten Ziegeler wrote:
Hi,
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)
Thoughts?
Regards
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
