Mark liquibase-maven-plugin logging configuration as deprecated

[nvoxland]

Description

In 4.0, we started ignoring the liquibase-maven-plugin configuration tag in favor of relying on the built-in maven logging system.

That means that liquibase now respects the -q, -X and -e flags and/or the ${maven.home}/conf/logging/simplelogger.properties file file.

But, we just silently ignored the configuration users had.

This PR outputs an ERROR level log if the configuration is set letting users know it is being ignored.

New behavior

• If there is no configuration, there is no message
• If you have a configuration in your maven project, log a {{ The liquibase-maven-plugin now manages logging via the standard maven logging config, not the 'logging' configuration. Use the -q, -X and -e flags or configure Maven logging properties file following these instructions: https://maven.apache.org/mavenlogging.html}} ERRORlevel message

Dev Handoff Notes (Internal Use)

Links

• Fixed Issue: Stand alone PR
• Test Results: https://github.com/liquibase/liquibase/pull/2261/checks

Testing

• Steps to Reproduce: See above
• Guidance:
  • Impact: any liquibase-maven-plugin commands

Dev Verification

Verified message when and only when the logging configuration is set.

Test Requirements (Liquibase Internal QA)

Manual Tests

Verify that log message is displayed when with global configuration.

• specify <liquibase.logging>debug</liquibase.logging> in your pom.xml file under properties section
• execute any liquibase command
• ERROR level log message is displayed

Verify that log message is displayed when with liquibasemavenplagin configuration.

• remove global logging configuration in pom.xml file
• specify logging configuration in pom.xml file under liquibase-maven-plagin section

<plugin>
		<groupId>org.liquibase</groupId>
		<artifactId>liquibase-maven-plugin</artifactId>
		<version>0-SNAPSHOT</version>
		<configuration>
			<logging>debug</logging>
		</configuration>
</plugin>

• execute any liquibase command
• ERROR level log message is displayed

Verify that message is not displayed when configuration is not specified.

• make sure that there is no configuration specified in pom.xml file
• execute any liquibase command
• no message is displayed

Automated Tests

No new functional tests required for this fix.

┆Issue is synchronized with this Jira Bug by Unito
┆fixVersions: Community 4.x