Resolved by adding the following exclusion in the dependencies (of pom.xml) that caused conflict.
<exclusions>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
</exclusions>
More Related Contents:
- Exclude all transitive dependencies of a single dependency
- Sharing Test code in Maven
- How do I execute a program using Maven?
- Specify system property to Maven project
- Maven test dependency in multi module project
- Can I use the path to a Maven dependency as a property?
- How to exclude a module from a Maven reactor build?
- How can I tell jaxb / Maven to generate multiple schema packages?
- Using the Nexus rest API to get latest artifact version for given groupid/artifactId
- Maven – how can I add an arbitrary classpath entry to a jar?
- m2e lifecycle-mapping not found
- Setting Java heap space under Maven 2 on Windows
- Setting default values for custom Maven 2 properties
- maven report on licenses your project depends on [closed]
- Use public maven repository with ivy
- Using Maven for multiple deployment environment (production/development)
- Maven copy local file to remote server using SSH
- Is there a way to tell surefire to skip tests in a certain package?
- What is the difference between “mvn deploy” to a local repo and “mvn install”?
- Maven: how to do parallel builds?
- Is it possible to override the configuration of a plugin already defined for a profile in a parent POM?
- Maven: downloading files from url
- maven2: excluding directory from WAR
- mvn archetype:generate does not work-no plugin found for prefix ‘archetype’
- Maven: Including jar not found in public repository
- Maven – Add directory to classpath while executing tests
- Add maven-build-classpath to plugin execution classpath
- Maven plugin executing another plugin
- maven in 5 min not working
- Disable the default-jar execution