Hi Oliver,
if we call it "oak", we probably would have to also create a sub folder
contrib/oak (as all modules in contrib/jcr have the group id
org.apache.sling.jcr)... that's probably more confusing than just
leaving it in contrib/jcr (having jcr and oak side by side when oak also
provides the jcr). Robert, what do you think?
Regards
Georg
On 2016-09-07 22:33, Oliver Lietz wrote:
On Monday 01 August 2016 13:37:26 Robert Munteanu wrote:
Hi Georg,
Hi,
On Sat, 2016-07-30 at 10:14 +0200, Georg Henzler wrote:
> Hi all,
>
> with SLING-5768/SLING-5891 fixed and the documentation in
> https://sling.apache.org/documentation/bundles/sling-oak-restrictions
> .html
> we have everything needed to cut a first release IMHO - could
> someone
> take care of it?
I think we need to clarify two issues:
1. Bundle name and location
Right now the Bundle-SymbolicName is org.apache.sling.sling-oak-
restrictions and it's placed under contrib/extensions . I would rather
see it named org.apache.sling.jcr.oak-restrictions and placed under
contrib/jcr .
the bundle is not using JCR API but Oak API only
(org.apache.jackrabbit.oak.spi.security.authorization.restriction).
Shouldn't
we go for a simple module and package name
org.apache.sling.oak.restriction?
Regards,
O.
2. Naming of the restrictions
There was some discussion related to the name of the
'sling:resourceTypesWithChildren' restriction [1]. I want to make sure
that we have agreement that this is the best name what we could come
up
with before releasing and committing to this name "forever".
Once these are agreed on, I can take care of an initial release.
Robert
[1]: https://issues.apache.org/jira/browse/SLING-5768
