On Thu, 2019-03-21 at 11:57 +0100, Simone Tripodi 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
I would sugggest that we use on of the artifactIds org.apache.sling.feature.content-package-converter org.apache.sling.feature.cpconverter (and the associated update to the proposed repository name). This would match the existing feature model related projects at https://github.com/apache/?utf8=%E2%9C%93&q=sling-feature&type=&language= This is only suggestion, otherwise my vote is +1 Thanks, Robert > 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
signature.asc
Description: This is a digitally signed message part
