ppkarwasz commented on code in PR #2120: URL: https://github.com/apache/logging-log4j2/pull/2120#discussion_r1434078600
########## src/changelog/.2.x.x/simplify_configuration_after_bnd_7_update.xml: ########## @@ -0,0 +1,25 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- + ~ Licensed to the Apache Software Foundation (ASF) under one or more + ~ contributor license agreements. See the NOTICE file distributed with + ~ this work for additional information regarding copyright ownership. + ~ The ASF licenses this file to you under the Apache License, Version 2.0 + ~ (the "License"); you may not use this file except in compliance with + ~ the License. You may obtain a copy of the License at + ~ + ~ http://www.apache.org/licenses/LICENSE-2.0 + ~ + ~ Unless required by applicable law or agreed to in writing, software + ~ distributed under the License is distributed on an "AS IS" BASIS, + ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + ~ See the License for the specific language governing permissions and + ~ limitations under the License. + --> +<entry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; + xmlns="http://logging.apache.org/log4j/changelog"; + xsi:schemaLocation="http://logging.apache.org/log4j/changelog https://logging.apache.org/log4j/changelog-0.1.3.xsd"; + type="updated"> + <description format="asciidoc"> + Simplify BND configuration after upgrade from version 6.4.1 to 7.0.0. Review Comment: Technically it **is** a dependency update: it should have **no** effect on the user. The only reason I add it to the changelog is that these kind of things _might_ contain errors and I want to be plenty transparent about the "no-op" changes that occurred. Maybe it should be a "fixed" change, since it actually fixes the usage of Conversant Media Disruptor. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
