Responding to my own email to conserve anyone else's effort.
I fired off my last response before doing a cursory web search :/
It looks like, in the old old days, one way to effect a node
type change is to stop Sling, delete the custom_nodetypes.xml
file, and restart, causing the node types to be
Thank you for the response, Stefan!
I was surprised about the behavior for 1. below and I'm positive that I have
seen the
new code activate immediately before also. I'll look into this further.
I'm not surprised what you describe about #2. When you say "remove this
definition
manually", what
>1.) Are there cases where I would need to shut down and restart Sling in
>order for an updated version of the bundle to be functional. What I'm
>seeing today is that I make a few code changes, do a "mvn clean install
>sling:install", observe that the bundle gets installed, but when I make use
Hi,
there is the "Felix FileInstall" bundle which allows installation of
bundles in a scanned directory.
Sling's OSGi Installer has also a "FileInstall Provider" which enables
similar functionality I assume.
Does it make sense to use the Felix FileInstall way or should we use the
Sling OSGi
