# Using the shaded JAR The default driver JAR depends on [Netty](http://netty.io/), which is used internally for networking. This explicit dependency can be a problem if your application already uses another Netty version. To avoid conflicts, we provide a “shaded” version of the JAR, which bundles the Netty classes under a different package name: ```xml com.scylladb scylla-driver-core 3.11.5.0 shaded io.netty * io.dropwizard.metrics metrics-core ``` If you also use the mapper, you need to remove its dependency to the non-shaded JAR: ```xml com.scylladb scylla-driver-core 3.11.5.0 shaded io.netty * io.dropwizard.metrics metrics-core com.scylladb scylla-driver-mapping 3.11.5.0 com.scylladb scylla-driver-core ``` ## Limitations When using the shaded jar, it is not possible to configure the Netty layer. Extending [NettyOptions](https://java-driver.docs.scylladb.com/scylla-3.12.1.x/api/com/datastax/driver/core/NettyOptions.html) is not an option because `NettyOptions` API exposes Netty classes, and as such it should only be extended by clients using the non-shaded version of driver. Attempting to extend `NettyOptions` with shaded Netty classes is not supported, and in particular for OSGi applications, it is likely that such a configuration would lead to compile and/or runtime errors. Also, with shaded Netty classes, it is not possible to benefit from [Netty native transports](http://netty.io/wiki/native-transports.html). It is therefore normal to see the following log line when the driver starts and detects that shaded Netty classes are being used: ```none Detected shaded Netty classes in the classpath; native epoll transport will not work properly, defaulting to NIO. ```