Hello all,
I was looking into bundle resource provider on sling 9
"/system/console/bundleresources" but when trying to navigate to the
path i.e : view the content of /libs/sling/sightly/js this will only
show one level but not sub levels. (see attached)
I also get a nice exception in the
Hello all,
I'm currently using this code in my bundle
http://svn.apache.org/viewvc/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/repository/SystemUsersInitializer.java?view=markup=1727946
to execute a repoinit file to create service users.
I wanted
Maybe a solution would be
- deprecate / remove the method ( to avoid old code to run as admin)
- rename the class / method and add an info to the log
in this way we make sure that old code gets migrated to service users,
and the places where it really makes sense to use admin user, the
Hello,
I think this is intrinsic to the File Installer Provider,
one idea that comes to my mind is that you could try is to upload the
packe into the repository prior to removing it from the install dir.
In this way osgi still has an candidate for that artifact.
Of course you could also add
Hello all,
I have this questions about how to run, monitor, verify online
compaction in sling
Regards
Andres
Hey Chris
I think defining an extension as part of the path would cause this not
to work,
since the extension is not part of the requests path (your examples)
as fas as I can remember, this should look more like:
"/content/path/*:text/plain" this means apply the filter for every path
bellow
