ShortenedThrowableConverter: <exclude> and <exclusions> are mutually exclusive #876
Labels
warn/behavior-change
Breaking change of publicly advertised behavior
Milestone
Suppose the following configuration:
Using the
<exclusions>
with an environment variable is an easy way to configure additional exclusion patterns in addition to those already configured in the XML file. However, it happens that<exclusions>
clears the exclusions already configured and replace them with new values. This sample configuration results in only TWO exclusion patterns with the first one being ignored...To avoid confusion the
<exclusions>
keyword should ADD new patterns instead of replacing those already defined.The text was updated successfully, but these errors were encountered: