You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by GitBox <gi...@apache.org> on 2019/08/21 16:10:09 UTC

[GitHub] [sling-org-apache-sling-feature] bosschaert commented on a change in pull request #14: SLING-8647: Provide policies for configuration merging

bosschaert commented on a change in pull request #14: SLING-8647: Provide policies for configuration merging
URL: https://github.com/apache/sling-org-apache-sling-feature/pull/14#discussion_r316273043
 
 

 ##########
 File path: src/main/java/org/apache/sling/feature/builder/BuilderContext.java
 ##########
 @@ -64,6 +64,18 @@
     /** Used in override rule to match all coordinates */
     public static final String COORDINATE_MATCH_ALL = "*";
 
+    /** Used to handle configuration merging - fail the merge when there is a clash for a PID - this is the default */
+    public static final String CONFIG_FAIL_ON_CLASH = "CLASH";
+
+    /** Used to handle configuration merging - fail the merge only when there is a clash on a property level */
+    public static final String CONFIG_FAIL_ON_PROPERTY_CLASH = "PROPERTY_CLASH";
+
+    /** Used to handle configuration merging - use the latest configuration, but don't merge */
+    public static final String CONFIG_USE_LATEST = "USE_LATEST";
 
 Review comment:
   Is there also an opposite of this, in case you want to force not to use the latest be keep the 'oldest'?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services