You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2019/04/12 15:33:00 UTC
[jira] [Created] (SLING-8351) sling-mock NodeTypeDefinitionScanner:
avoid problems with same node type is registered mulitple times with
different definitions
Stefan Seifert created SLING-8351:
-------------------------------------
Summary: sling-mock NodeTypeDefinitionScanner: avoid problems with same node type is registered mulitple times with different definitions
Key: SLING-8351
URL: https://issues.apache.org/jira/browse/SLING-8351
Project: Sling
Issue Type: Improvement
Affects Versions: Testing Sling Mock 2.3.6
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Fix For: Testing Sling Mock 2.3.8
the NodeTypeDefinitionScanner automatically detects all node types listed in {{Sling-Nodetypes}} property in any MANIFEST.MF found in the classpath. however, the order in which the node types are found and registered is not predictable.
if multiple cnd files found in this way register the same node type and expect to be executed in a defined order this may fail in sling-mock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)