Hi Daniel,thanks a lot for jumping in, 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:29 PM Daniel Klco <[email protected]> wrote:
Perhaps I am too confused as to the purpose of the feature model, I was
under the impression that it was a method for building Sling applications
rather than content / code deployments.
The Sling Feature model supports both, it is a method to build Sling
applications AND content / code deployments, see the "Built-in
extension: content-packages" on Sling Feature model documentation[1]
If it is in fact for code deployments as Konrad asks, what is the
deployment method and do we need other tooling around build / IDE support
as well?
The purpose of the tool is providing an easy way which, for existing
content packages, is able to clearly separate what is pure content to
OSGi bundles & configuration: mixing content-packages (with embedded
packages) can be confusing, with the Sling Feature is clear what is
the app and what is the content.
That tool can be useful to migrate to the new Sling Feature launcher.
IMO -- I'd love to get away from content packages, I mean it's still
1000x
better than when I worked with Documentum / Drupal / Wordpress in terms
of
ETL'ing content but as a code deployment method, it does not contain
enough
metadata to evaluate the success of the code deployments and therefore
doesn't enable "fail fast" builds (e.g. you can't tell if a bundle fails
to
start or a configuration doesn't bind besides checking the OSGi console).
I fear we can not completely replace content-packages with Sling
Feature Model due to the fact the Feature describes the application
layer only, but it is a big step ahead already for the separation of
concerns.
HTH!
+1 for having a conversion path and would love to hear more.
Thanks!!! :)
~Simo
[1] https://github.com/apache/sling-org-apache-sling-feature
On Thu, Mar 21, 2019 at 8:00 AM 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.
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.
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
