Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
// TODO does it harm?!?
addSystemUserPath(formatter, systemUser.getPath());
where the method looks as follows:
private final void addSystemUserPath(Formatter formatter, RepoPath path) { if (preProvidedSystemPaths.add(path)) { formatter.format("create path (rep:AuthorizableFolder) %s%n", path); } }
i would strong recommend to drop that. the content-package-feature-model-converter already has quite some hardcoded stuff.... how the intermediate path argument passed to UserManager.createSystemUser(String id, String intermediatePath) is used and what node types are used to create the hierarchy should be considered an implementation detail and it doesn't make sense IMHO to eagerly create the tree structure in a feature like this. in fact i would consider this a bug that may sooner or later cause the converter to fail during repo-init execution.
btw: the comment already implies that the author was not sure of the usefulness.... why not verifying and fixing the code or dropping the TODO before releasing the module?
Attachments
Issue Links
- blocks
-
SLING-9692 Add support for principal-based access control entries
- Closed
- relates to
-
SLING-9962 DefaultAclManager#addPaths prone to causing ConstraintViolationException
- Closed
- links to