Hi Carsten, can you provide some insights on timing wrt Felix Snapshot dependencies. When we plugged together the demo we still had a few dependencies on unreleased artifacts for the OSGi R7 work.
I would rather see this change happening yesterday than tomorrow to start working on how the model can be maintained and operated over time and add the corresponding missing pieces for this as touched in the presentation (e.g. Deployment Admin & optimizations of installer and packagetransformer for Sling). As some of that specifically should work properly hand-in-hand with the builder and analyzer part I would want to avoid working against a heavily moving target (assuming that SNAPSHOT is not settled at all). Cheers Dominik On Thu, Oct 5, 2017 at 4:10 PM, Julian Sedding <jsedd...@gmail.com> wrote: > Hi Bertrand > > I suppose it would be > > cat provisioning-model | jsmin | jq . > > I have not tested this, however. > > Regards > Julian > > > On Thu, Oct 5, 2017 at 3:39 PM, Bertrand Delacretaz > <bdelacre...@apache.org> wrote: > > On Thu, Oct 5, 2017 at 11:39 AM, Julian Sedding <jsedd...@gmail.com> > wrote: > >> ...lets stick with JSON + comments... > > > > Is that format accepted by JSON tools? Can I for example do > > > > cat provisioning-model | jq . > > > > ? > > > > Otherwise I fear the format combines the worst of both worlds: hard > > for humans to read and write (JSON) and not directly suitable for > > machine processing. In which case I suggest rediscussing the comments > > format/schema to make sure the result is pure JSON - maybe with > > _comment_ elements that tools can easily ignore. > > > > -Bertrand >
