New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two versions of Netty listed as dependencies -- deployment errors #404
Comments
Hi,
you can refer following pom.xml for dependency exclusion: Thanks On Sun, Sep 22, 2013 at 1:54 AM, sdnakhla notifications@github.com wrote:
Thanks and Regards |
Yes, if I manually exclude the Netty libraries it deploys fine. However, this is a less-than-ideal situation. |
No need to manually exclude jars,
from pom.xml. It should work for you. -Vivek |
I agree with @sdnakhla. Working with exclusions is not the ideal solution! When using a library, I expect it to hide details such as circular or repeated dependencies. In this particular case, who's importing different versions of Netty.IO? Different Kundera modules or some dependencies of Kundera modules? |
This version of netty is bought in by apache Cassandra jar. I assume it might be used for running daemon threads? |
The thing is with JBoss that already includes Netty.IO, right @sdnakhla? If it is, then kundera-cassandra should stay as is. |
When using Maven to manage dependencies for Kundera with Cassandra as a datastore, it appears to be pulling down two separate versions of the Netty library. These, consequently, end up imported into an EAR and cause deployment errors on JBoss EAP 6.1. Here's what I see during the Maven build:
...
[INFO] Copying artifact[jar:com.github.stephenc:jamm:0.2.5] to[lib/jamm-0.2.5.jar]
[INFO] Copying artifact[jar:io.netty:netty:3.5.9.Final] to[lib/netty-3.5.9.Final.jar]
[INFO] Copying artifact[jar:org.apache.cassandra:cassandra-clientutil:1.2.4] to[lib/cassandra-clientutil-1.2.4.jar]
[INFO] Copying artifact[jar:org.jboss.netty:netty:3.2.8.Final] to[lib/netty-3.2.8.Final.jar]
[INFO] Copying artifact[jar:org.slf4j:slf4j-api:1.7.2] to[lib/slf4j-api-1.7.2.jar]
...
And the subsequent error during deployment:
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.pojo."org.jboss.netty.internal.LoggerConfigurator".DESCRIBED is already registered
The text was updated successfully, but these errors were encountered: