Hi Konrad,thanks a lot for joining the discussion, very
appreciated!Please read my inline comments, all the
best!~Simohttp://people.apache.org/~simonetripodi/http://www.99soft.org/
On Thu, Mar 21, 2019 at 1:00 PM Konrad Windszus <[email protected]> wrote:
>
> Great and useful tool.
> Some questions around that:
>
> 1. From the readme at 
> https://github.com/apache/sling-whiteboard/tree/master/content-package-2-feature-model#supported-configurations
>  
> <https://github.com/apache/sling-whiteboard/tree/master/content-package-2-feature-model#supported-configurations>
>  it is not 100% clear if really all configs are converted to JSON format. 
> Maybe we can make an explicit statement about that.

I'll clarify it - yes, all OSGi configuration formats are supported
and be converted to the Sling Feature convention.

> 2. Also what I am lacking is how to deploy a FeatureModel to an already 
> started Sling instance. AFAIK this is currently not yet there which is not a 
> problem, but it is also worth mentioning it in the readme. This is especially 
> crucial for content-packages as they are often deployed to an already 
> existing instance. So an explicit "Deployment" section would be highly 
> appreciated.
>

I'd suggest to move that part of the conversation to a separated,
dedicated thread - in the meanwhile I can point you to the Sling
Feature[1] documentation.
HTH!
~Simo

[1] https://github.com/apache/sling-org-apache-sling-feature-launcher

> Thanks,
> Konrad
>
> > On 21. Mar 2019, at 11:57, Simone Tripodi <[email protected]> wrote:
> >
> > Hi all,
> > this email to propose to continue a tool development I started from
> > the whiteboard[1] as a regular sub-project.
> >
> > The tool I started developing is about converting existing plain old
> > JCR content-packages[2] to the new Sling Feature Model[3] files +
> > bundles.
> >
> > Benefits of adopting this tool will make easier the transition for JCR
> > users transitioning to the newer Sling technology.
> >
> > Status of the whiteboard:
> > The tool is able to convert pilot content-packages and contains a test
> > coverage of +60%, all supported features are described on the README,
> > it already support being packaged as a standalone-CLI tool.
> >
> > Proposal for the new Git repository:
> > https://github.com/apache/sling-org-apache-sling-cp2fm
> >
> > Vote will be open for 72 hours and will close ~ on March the 24th 11:40am
> >
> > [ ] +1!!!
> > [ ] +/-0, fine, but consider to clarify before...
> > [ ] -1, nope, because... (and please explain why)
> >
> > Many thanks in advance!
> > -Simo
> >
> > [1] 
> > https://github.com/apache/sling-whiteboard/tree/master/content-package-2-feature-model
> > [2] http://jackrabbit.apache.org/filevault/
> > [3] https://github.com/apache/sling-org-apache-sling-feature
> >
> > http://people.apache.org/~simonetripodi/
> > http://twitter.com/simonetripodi
>

Reply via email to