Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DAT-16050 Remove warnings from liquibase-parent-pom (#71)
* chore(pom.xml): update liquibase-parent-pom version from 0.3.0-SNAPSHOT to 0.2.6-SNAPSHOT for compatibility reasons feat(pom.xml): add proguard rules to keep classes from software.amazon and io.netty packages to prevent obfuscation errors * chore(pom.xml): update jackson version to 2.15.2 for jackson-databind dependency chore(pom.xml): remove unused commons-io dependency chore(pom.xml): remove unused slf4j dependencies chore(pom.xml): remove unused jackson-dataformat-yaml dependency chore(pom.xml): remove optimize flag from maven-compiler-plugin configuration chore(pom.xml): add systemPropertyVariables configuration to maven-surefire-plugin for spock-reports output directory chore(pom.xml): add redirectTestOutputToFile and reportFormat configuration to maven-failsafe-plugin * chore(pom.xml): reformat indentation and spacing for better readability * chore(pom.xml): add proguard rules to keep specific classes from being obfuscated The changes in this commit add ProGuard rules to the pom.xml file. These rules specify that certain classes should be kept from being obfuscated during the build process. The classes that are being kept include those from the following packages: io.netty, org.reactivestreams, com.google, com.fasterxml.jackson, org.apache, org.bouncycastle, and org.slf4j. The reason for these changes is to ensure that the specified classes are not obfuscated, as they may be required for the proper functioning of the application or for compatibility with other libraries or frameworks. By keeping these classes, we can avoid potential issues that may arise from obfuscating them. * chore(pom.xml): update commons-io version to 2.11.0 for dependency management feat(pom.xml): add commons-io dependency with version 2.11.0 for file input/output operations
- Loading branch information