# Jmxri and jmxtools Maven artefacts

**URL:** <https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938>\
**Category:** Elasticsearch\
**Created:** [May 3, 2010, 3:33pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938 "2010-05-03T15:33:25Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 3, 2010, 3:33pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/1 "2010-05-03T15:33:25Z")

</div>

Hi,

I am trying to use elasticsearch in maven project. I built 0.7.0-snapshot  
locally and installed into local maven repo. But when added this dependency  
into my maven project then it requires transitive dependencies like  
com.sun.jdmk:jmxtools:pom:1.2.1 and com.sun.jmx:jmxri:pom:1.2.1. However,  
these jars are not available in public maven repos due to licencing issues.  
One easy solution seems to be adding exclusions into pom.xml

```
<dependencies>
    <dependency>
        <groupId>org.elasticsearch</groupId>
        <artifactId>elasticsearch</artifactId>
        <version>0.7.0-SNAPSHOT</version>
        <exclusions>
            <exclusion>
                <groupId>com.sun.jmx</groupId>
                <artifactId>jmxri</artifactId>
            </exclusion>
            <exclusion>
                <groupId>com.sun.jdmk</groupId>
                <artifactId>jmxtools</artifactId>
            </exclusion>
        </exclusions>
    </dependency>
</dependencies>

```

The question is if I elasticsearch will need this jars at some point in  
time. Does anybody have experience developing with ES using maven? Are those  
JARs needed?

Regards,  
Lukas

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 3, 2010, 4:50pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/2 "2010-05-03T16:50:32Z")

</div>

Can you run the maven dependency tree thingy to see where it is coming from?  
There is no need for it for elasticsarch (here is the pom:  
[http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Hi,
> 
> I am trying to use elasticsearch in maven project. I built 0.7.0-snapshot  
> locally and installed into local maven repo. But when added this dependency  
> into my maven project then it requires transitive dependencies like  
> com.sun.jdmk:jmxtools:pom:1.2.1 and com.sun.jmx:jmxri:pom:1.2.1. However,  
> these jars are not available in public maven repos due to licencing issues.  
> One easy solution seems to be adding exclusions into pom.xml
> 
> ```
> <dependencies>
> <dependency>
> <groupId>org.elasticsearch</groupId>
> <artifactId>elasticsearch</artifactId>
> <version>0.7.0-SNAPSHOT</version>
> <exclusions>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> </dependencies>
> 
> ```
> 
> The question is if I elasticsearch will need this jars at some point in  
> time. Does anybody have experience developing with ES using maven? Are those  
> JARs needed?
> 
> Regards,  
> Lukas

---

<div class="post-metadata">

**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\
**Post date:** [May 3, 2010, 6:19pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/3 "2010-05-03T18:19:53Z")

</div>

If it turns out to be coming from log4j you can safely exclude them.

On Mon, May 3, 2010 at 5:50 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Can you run the maven dependency tree thingy to see where it is coming  
> from? There is no need for it for elasticsarch (here is the pom:  
> [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> ).
> 
> On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:
> 
> > Hi,
> > 
> > I am trying to use elasticsearch in maven project. I built 0.7.0-snapshot  
> > locally and installed into local maven repo. But when added this dependency  
> > into my maven project then it requires transitive dependencies like  
> > com.sun.jdmk:jmxtools:pom:1.2.1 and com.sun.jmx:jmxri:pom:1.2.1. However,  
> > these jars are not available in public maven repos due to licencing issues.  
> > One easy solution seems to be adding exclusions into pom.xml
> > 
> > ```
> > <dependencies>
> > <dependency>
> > <groupId>org.elasticsearch</groupId>
> > <artifactId>elasticsearch</artifactId>
> > <version>0.7.0-SNAPSHOT</version>
> > <exclusions>
> > <exclusion>
> > <groupId>com.sun.jmx</groupId>
> > <artifactId>jmxri</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>com.sun.jdmk</groupId>
> > <artifactId>jmxtools</artifactId>
> > </exclusion>
> > </exclusions>
> > </dependency>
> > </dependencies>
> > 
> > ```
> > 
> > The question is if I elasticsearch will need this jars at some point in  
> > time. Does anybody have experience developing with ES using maven? Are those  
> > JARs needed?
> > 
> > Regards,  
> > Lukas

## --

Paul Loy  
[paul@keteracel.com](mailto:paul@keteracel.com)  
[http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 3, 2010, 6:46pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/4 "2010-05-03T18:46:43Z")

</div>

Yes, they come from log4j

[INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
[INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
[INFO] +-  
org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
[INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
[INFO] +- log4j:log4j:jar:1.2.15:compile  
[INFO] | +- javax.mail:mail:jar:1.4:compile  
[INFO] | | - javax.activation:activation:jar:1.1:compile  
[INFO] | +- javax.jms:jms:jar:1.1:compile  
[INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
[INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
[INFO] +- jline:jline:jar:0.9.94:compile  
[INFO] | - junit:junit:jar:3.8.1:compile  
[INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
[INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
[INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
[INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
[INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
[INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
[INFO] +- joda-time:joda-time:jar:1.6:compile  
[INFO] - org.yaml:snakeyaml:jar:1.6:compile

2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)

> If it turns out to be coming from log4j you can safely exclude them.
> 
> On Mon, May 3, 2010 at 5:50 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> 
> > Can you run the maven dependency tree thingy to see where it is coming  
> > from? There is no need for it for elasticsarch (here is the pom:  
> > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > ).
> > 
> > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > 
> > > Hi,
> > > 
> > > I am trying to use elasticsearch in maven project. I built 0.7.0-snapshot  
> > > locally and installed into local maven repo. But when added this dependency  
> > > into my maven project then it requires transitive dependencies like  
> > > com.sun.jdmk:jmxtools:pom:1.2.1 and com.sun.jmx:jmxri:pom:1.2.1. However,  
> > > these jars are not available in public maven repos due to licencing issues.  
> > > One easy solution seems to be adding exclusions into pom.xml
> > > 
> > > ```
> > > <dependencies>
> > > <dependency>
> > > <groupId>org.elasticsearch</groupId>
> > > <artifactId>elasticsearch</artifactId>
> > > <version>0.7.0-SNAPSHOT</version>
> > > <exclusions>
> > > <exclusion>
> > > <groupId>com.sun.jmx</groupId>
> > > <artifactId>jmxri</artifactId>
> > > </exclusion>
> > > <exclusion>
> > > <groupId>com.sun.jdmk</groupId>
> > > <artifactId>jmxtools</artifactId>
> > > </exclusion>
> > > </exclusions>
> > > </dependency>
> > > </dependencies>
> > > 
> > > ```
> > > 
> > > The question is if I elasticsearch will need this jars at some point in  
> > > time. Does anybody have experience developing with ES using maven? Are those  
> > > JARs needed?
> > > 
> > > Regards,  
> > > Lukas
> 
> ## --
> 
> Paul Loy  
> [paul@keteracel.com](mailto:paul@keteracel.com)  
> [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\
**Post date:** [May 3, 2010, 6:58pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/5 "2010-05-03T18:58:50Z")

</div>

yeah, just exclude them:

> **[Resolving log4j 1.2.15 dependency problems in Maven using exclusions »...](https://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)**
>
> unitstep.net: the home page of peter chng, a software developer based in ontario, canada.

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Yes, they come from log4j
> 
> [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> [INFO] +-  
> org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> [INFO] +- log4j:log4j:jar:1.2.15:compile  
> [INFO] | +- javax.mail:mail:jar:1.4:compile  
> [INFO] | | - javax.activation:activation:jar:1.1:compile  
> [INFO] | +- javax.jms:jms:jar:1.1:compile  
> [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> [INFO] +- jline:jline:jar:0.9.94:compile  
> [INFO] | - junit:junit:jar:3.8.1:compile  
> [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> [INFO] +- joda-time:joda-time:jar:1.6:compile  
> [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> 
> 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> 
> If it turns out to be coming from log4j you can safely exclude them.
> 
> > On Mon, May 3, 2010 at 5:50 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> > 
> > > Can you run the maven dependency tree thingy to see where it is coming  
> > > from? There is no need for it for elasticsarch (here is the pom:  
> > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > ).
> > > 
> > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > 
> > > > Hi,
> > > > 
> > > > I am trying to use elasticsearch in maven project. I built  
> > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > this dependency into my maven project then it requires transitive  
> > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > exclusions into pom.xml
> > > > 
> > > > ```
> > > > <dependencies>
> > > > <dependency>
> > > > <groupId>org.elasticsearch</groupId>
> > > > <artifactId>elasticsearch</artifactId>
> > > > <version>0.7.0-SNAPSHOT</version>
> > > > <exclusions>
> > > > <exclusion>
> > > > <groupId>com.sun.jmx</groupId>
> > > > <artifactId>jmxri</artifactId>
> > > > </exclusion>
> > > > <exclusion>
> > > > <groupId>com.sun.jdmk</groupId>
> > > > <artifactId>jmxtools</artifactId>
> > > > </exclusion>
> > > > </exclusions>
> > > > </dependency>
> > > > </dependencies>
> > > > 
> > > > ```
> > > > 
> > > > The question is if I elasticsearch will need this jars at some point in  
> > > > time. Does anybody have experience developing with ES using maven? Are those  
> > > > JARs needed?
> > > > 
> > > > Regards,  
> > > > Lukas
> > 
> > ## --
> > 
> > Paul Loy  
> > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

## --

Paul Loy  
[paul@keteracel.com](mailto:paul@keteracel.com)  
[http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 3, 2010, 7:03pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/6 "2010-05-03T19:03:30Z")

</div>

Good, but wouldn't it be better to get rid of log4j at all? Can't ES just  
use slf4j without log4j bridge?  
Lukas

On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:

> yeah, just exclude them:  
> [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> 
> On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:
> 
> > Yes, they come from log4j
> > 
> > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > [INFO] +-  
> > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > [INFO] +- jline:jline:jar:0.9.94:compile  
> > [INFO] | - junit:junit:jar:3.8.1:compile  
> > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > 
> > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > 
> > If it turns out to be coming from log4j you can safely exclude them.
> > 
> > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> > > 
> > > > wrote:
> > > 
> > > > Can you run the maven dependency tree thingy to see where it is coming  
> > > > from? There is no need for it for elasticsarch (here is the pom:  
> > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > ).
> > > > 
> > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > this dependency into my maven project then it requires transitive  
> > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > exclusions into pom.xml
> > > > > 
> > > > > ```
> > > > > <dependencies>
> > > > > <dependency>
> > > > > <groupId>org.elasticsearch</groupId>
> > > > > <artifactId>elasticsearch</artifactId>
> > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > <exclusions>
> > > > > <exclusion>
> > > > > <groupId>com.sun.jmx</groupId>
> > > > > <artifactId>jmxri</artifactId>
> > > > > </exclusion>
> > > > > <exclusion>
> > > > > <groupId>com.sun.jdmk</groupId>
> > > > > <artifactId>jmxtools</artifactId>
> > > > > </exclusion>
> > > > > </exclusions>
> > > > > </dependency>
> > > > > </dependencies>
> > > > > 
> > > > > ```
> > > > > 
> > > > > The question is if I elasticsearch will need this jars at some point in  
> > > > > time. Does anybody have experience developing with ES using maven? Are those  
> > > > > JARs needed?
> > > > > 
> > > > > Regards,  
> > > > > Lukas
> > > 
> > > ## --
> > > 
> > > Paul Loy  
> > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> 
> ## --
> 
> Paul Loy  
> [paul@keteracel.com](mailto:paul@keteracel.com)  
> [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 3, 2010, 8:32pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/7 "2010-05-03T20:32:20Z")

</div>

If you have a look at the pom (that I linked in the previous mail), then ES  
does not rely on either slf4j or log4j (it has "yet another" lightweight  
logging abstarction). Are you using gradle install or are you resolving it  
from elasticsearch snapshot repo? If you will notice, you will see that  
elasticsearch only relies on netty and lucene (much work has been done in  
this version to reduce and jarjar the deps).

On Mon, May 3, 2010 at 10:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Good, but wouldn't it be better to get rid of log4j at all? Can't ES just  
> use slf4j without log4j bridge?  
> Lukas
> 
> On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:
> 
> > yeah, just exclude them:  
> > [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> > 
> > On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > 
> > > Yes, they come from log4j
> > > 
> > > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > > [INFO] +-  
> > > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > > [INFO] +- jline:jline:jar:0.9.94:compile  
> > > [INFO] | - junit:junit:jar:3.8.1:compile  
> > > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > > 
> > > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > > 
> > > If it turns out to be coming from log4j you can safely exclude them.
> > > 
> > > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<  
> > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > 
> > > > > Can you run the maven dependency tree thingy to see where it is coming  
> > > > > from? There is no need for it for elasticsarch (here is the pom:  
> > > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > > ).
> > > > > 
> > > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > > this dependency into my maven project then it requires transitive  
> > > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > > exclusions into pom.xml
> > > > > > 
> > > > > > ```
> > > > > > <dependencies>
> > > > > > <dependency>
> > > > > > <groupId>org.elasticsearch</groupId>
> > > > > > <artifactId>elasticsearch</artifactId>
> > > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > > <exclusions>
> > > > > > <exclusion>
> > > > > > <groupId>com.sun.jmx</groupId>
> > > > > > <artifactId>jmxri</artifactId>
> > > > > > </exclusion>
> > > > > > <exclusion>
> > > > > > <groupId>com.sun.jdmk</groupId>
> > > > > > <artifactId>jmxtools</artifactId>
> > > > > > </exclusion>
> > > > > > </exclusions>
> > > > > > </dependency>
> > > > > > </dependencies>
> > > > > > 
> > > > > > ```
> > > > > > 
> > > > > > The question is if I elasticsearch will need this jars at some point  
> > > > > > in time. Does anybody have experience developing with ES using maven? Are  
> > > > > > those JARs needed?
> > > > > > 
> > > > > > Regards,  
> > > > > > Lukas
> > > > 
> > > > ## --
> > > > 
> > > > Paul Loy  
> > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> > 
> > ## --
> > 
> > Paul Loy  
> > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 3, 2010, 9:00pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/8 "2010-05-03T21:00:43Z")

</div>

I did gradle install and it produced elasticsearch-0.7.0-SNAPSHOT.jar along  
with pom file which includes compile time dependency on log4j and other  
libraries (see my second mail for full list). So if I have a maven project  
which has only one dependency, i.e.  
org.elasticsearch  
elasticsearch  
0.7.0-SNAPSHOT  
then I have to exclude  
  
javax.jms  
jms  
  
  
javax.mail  
mail  
  
  
com.sun.jmx  
jmxri  
  
  
com.sun.jdmk  
jmxtools  
  
explicitly.

Regards,  
Lukas

On Mon, May 3, 2010 at 10:32 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> If you have a look at the pom (that I linked in the previous mail), then ES  
> does not rely on either slf4j or log4j (it has "yet another" lightweight  
> logging abstarction). Are you using gradle install or are you resolving it  
> from elasticsearch snapshot repo? If you will notice, you will see that  
> elasticsearch only relies on netty and lucene (much work has been done in  
> this version to reduce and jarjar the deps).
> 
> On Mon, May 3, 2010 at 10:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> 
> > Good, but wouldn't it be better to get rid of log4j at all? Can't ES just  
> > use slf4j without log4j bridge?  
> > Lukas
> > 
> > On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:
> > 
> > > yeah, just exclude them:  
> > > [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> > > 
> > > On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > 
> > > > Yes, they come from log4j
> > > > 
> > > > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > > > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > > > [INFO] +-  
> > > > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > > > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > > > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > > > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > > > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > > > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > > > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > > > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > > > [INFO] +- jline:jline:jar:0.9.94:compile  
> > > > [INFO] | - junit:junit:jar:3.8.1:compile  
> > > > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > > > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > > > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > > > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > > > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > > > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > > > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > > > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > > > 
> > > > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > > > 
> > > > If it turns out to be coming from log4j you can safely exclude them.
> > > > 
> > > > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<  
> > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > 
> > > > > > Can you run the maven dependency tree thingy to see where it is coming  
> > > > > > from? There is no need for it for elasticsarch (here is the pom:  
> > > > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > > > ).
> > > > > > 
> > > > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > > 
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > > > this dependency into my maven project then it requires transitive  
> > > > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > > > exclusions into pom.xml
> > > > > > > 
> > > > > > > ```
> > > > > > > <dependencies>
> > > > > > > <dependency>
> > > > > > > <groupId>org.elasticsearch</groupId>
> > > > > > > <artifactId>elasticsearch</artifactId>
> > > > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > > > <exclusions>
> > > > > > > <exclusion>
> > > > > > > <groupId>com.sun.jmx</groupId>
> > > > > > > <artifactId>jmxri</artifactId>
> > > > > > > </exclusion>
> > > > > > > <exclusion>
> > > > > > > <groupId>com.sun.jdmk</groupId>
> > > > > > > <artifactId>jmxtools</artifactId>
> > > > > > > </exclusion>
> > > > > > > </exclusions>
> > > > > > > </dependency>
> > > > > > > </dependencies>
> > > > > > > 
> > > > > > > ```
> > > > > > > 
> > > > > > > The question is if I elasticsearch will need this jars at some point  
> > > > > > > in time. Does anybody have experience developing with ES using maven? Are  
> > > > > > > those JARs needed?
> > > > > > > 
> > > > > > > Regards,  
> > > > > > > Lukas
> > > > > 
> > > > > ## --
> > > > > 
> > > > > Paul Loy  
> > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> > > 
> > > ## --
> > > 
> > > Paul Loy  
> > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 3, 2010, 9:03pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/9 "2010-05-03T21:03:24Z")

</div>

Yea, I munge and remove these deps from the pom generated only on the upload  
task... . Need to check how to do it in the install phase as well..

On Tue, May 4, 2010 at 12:00 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> I did gradle install and it produced elasticsearch-0.7.0-SNAPSHOT.jar along  
> with pom file which includes compile time dependency on log4j and other  
> libraries (see my second mail for full list). So if I have a maven project  
> which has only one dependency, i.e.
> 
> ```
> <groupId>org.elasticsearch</groupId>
> <artifactId>elasticsearch</artifactId>
> <version>0.7.0-SNAPSHOT</version>
> 
> ```
> 
> then I have to exclude  
>   
> javax.jms  
> jms  
>   
>   
> javax.mail  
> mail
> 
> ```
> </exclusion>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> 
> ```
> 
> explicitly.
> 
> Regards,  
> Lukas
> 
> On Mon, May 3, 2010 at 10:32 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> 
> > If you have a look at the pom (that I linked in the previous mail), then  
> > ES does not rely on either slf4j or log4j (it has "yet another" lightweight  
> > logging abstarction). Are you using gradle install or are you resolving it  
> > from elasticsearch snapshot repo? If you will notice, you will see that  
> > elasticsearch only relies on netty and lucene (much work has been done in  
> > this version to reduce and jarjar the deps).
> > 
> > On Mon, May 3, 2010 at 10:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > 
> > > Good, but wouldn't it be better to get rid of log4j at all? Can't ES just  
> > > use slf4j without log4j bridge?  
> > > Lukas
> > > 
> > > On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:
> > > 
> > > > yeah, just exclude them:  
> > > > [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> > > > 
> > > > On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > 
> > > > > Yes, they come from log4j
> > > > > 
> > > > > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > > > > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > > > > [INFO] +-  
> > > > > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > > > > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > > > > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > > > > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > > > > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > > > > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > > > > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > > > > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > > > > [INFO] +- jline:jline:jar:0.9.94:compile  
> > > > > [INFO] | - junit:junit:jar:3.8.1:compile  
> > > > > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > > > > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > > > > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > > > > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > > > > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > > > > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > > > > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > > > > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > > > > 
> > > > > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > > > > 
> > > > > If it turns out to be coming from log4j you can safely exclude them.
> > > > > 
> > > > > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<  
> > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > 
> > > > > > > Can you run the maven dependency tree thingy to see where it is  
> > > > > > > coming from? There is no need for it for elasticsarch (here is the pom:  
> > > > > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > > > > ).
> > > > > > > 
> > > > > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > > > 
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > > > > this dependency into my maven project then it requires transitive  
> > > > > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > > > > exclusions into pom.xml
> > > > > > > > 
> > > > > > > > ```
> > > > > > > > <dependencies>
> > > > > > > > <dependency>
> > > > > > > > <groupId>org.elasticsearch</groupId>
> > > > > > > > <artifactId>elasticsearch</artifactId>
> > > > > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > > > > <exclusions>
> > > > > > > > <exclusion>
> > > > > > > > <groupId>com.sun.jmx</groupId>
> > > > > > > > <artifactId>jmxri</artifactId>
> > > > > > > > </exclusion>
> > > > > > > > <exclusion>
> > > > > > > > <groupId>com.sun.jdmk</groupId>
> > > > > > > > <artifactId>jmxtools</artifactId>
> > > > > > > > </exclusion>
> > > > > > > > </exclusions>
> > > > > > > > </dependency>
> > > > > > > > </dependencies>
> > > > > > > > 
> > > > > > > > ```
> > > > > > > > 
> > > > > > > > The question is if I elasticsearch will need this jars at some point  
> > > > > > > > in time. Does anybody have experience developing with ES using maven? Are  
> > > > > > > > those JARs needed?
> > > > > > > > 
> > > > > > > > Regards,  
> > > > > > > > Lukas
> > > > > > 
> > > > > > ## --
> > > > > > 
> > > > > > Paul Loy  
> > > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> > > > 
> > > > ## --
> > > > 
> > > > Paul Loy  
> > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [May 3, 2010, 9:11pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/10 "2010-05-03T21:11:54Z")

</div>

Should I create a new ticket for this? Actually, it is not a major issue as  
in normal case I would use public release with modified pom.

On Mon, May 3, 2010 at 11:03 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Yea, I munge and remove these deps from the pom generated only on the  
> upload task... . Need to check how to do it in the install phase as well..
> 
> On Tue, May 4, 2010 at 12:00 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> 
> > I did gradle install and it produced elasticsearch-0.7.0-SNAPSHOT.jar  
> > along with pom file which includes compile time dependency on log4j and  
> > other libraries (see my second mail for full list). So if I have a maven  
> > project which has only one dependency, i.e.
> > 
> > ```
> > <groupId>org.elasticsearch</groupId>
> > <artifactId>elasticsearch</artifactId>
> > <version>0.7.0-SNAPSHOT</version>
> > 
> > ```
> > 
> > then I have to exclude  
> >   
> > javax.jms  
> > jms  
> >   
> >   
> > javax.mail  
> > mail
> > 
> > ```
> > </exclusion>
> > <exclusion>
> > <groupId>com.sun.jmx</groupId>
> > <artifactId>jmxri</artifactId>
> > </exclusion>
> > <exclusion>
> > <groupId>com.sun.jdmk</groupId>
> > <artifactId>jmxtools</artifactId>
> > </exclusion>
> > 
> > ```
> > 
> > explicitly.
> > 
> > Regards,  
> > Lukas
> > 
> > On Mon, May 3, 2010 at 10:32 PM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)
> > 
> > > wrote:
> > 
> > > If you have a look at the pom (that I linked in the previous mail), then  
> > > ES does not rely on either slf4j or log4j (it has "yet another" lightweight  
> > > logging abstarction). Are you using gradle install or are you resolving it  
> > > from elasticsearch snapshot repo? If you will notice, you will see that  
> > > elasticsearch only relies on netty and lucene (much work has been done in  
> > > this version to reduce and jarjar the deps).
> > > 
> > > On Mon, May 3, 2010 at 10:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > 
> > > > Good, but wouldn't it be better to get rid of log4j at all? Can't ES  
> > > > just use slf4j without log4j bridge?  
> > > > Lukas
> > > > 
> > > > On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:
> > > > 
> > > > > yeah, just exclude them:  
> > > > > [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> > > > > 
> > > > > On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > 
> > > > > > Yes, they come from log4j
> > > > > > 
> > > > > > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > > > > > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > > > > > [INFO] +-  
> > > > > > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > > > > > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > > > > > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > > > > > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > > > > > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > > > > > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > > > > > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > > > > > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > > > > > [INFO] +- jline:jline:jar:0.9.94:compile  
> > > > > > [INFO] | - junit:junit:jar:3.8.1:compile  
> > > > > > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > > > > > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > > > > > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > > > > > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > > > > > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > > > > > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > > > > > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > > > > > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > > > > > 
> > > > > > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > > > > > 
> > > > > > If it turns out to be coming from log4j you can safely exclude them.
> > > > > > 
> > > > > > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<  
> > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > 
> > > > > > > > Can you run the maven dependency tree thingy to see where it is  
> > > > > > > > coming from? There is no need for it for elasticsarch (here is the pom:  
> > > > > > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > > > > > ).
> > > > > > > > 
> > > > > > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > > > > 
> > > > > > > > > Hi,
> > > > > > > > > 
> > > > > > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > > > > > this dependency into my maven project then it requires transitive  
> > > > > > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > > > > > exclusions into pom.xml
> > > > > > > > > 
> > > > > > > > > ```
> > > > > > > > > <dependencies>
> > > > > > > > > <dependency>
> > > > > > > > > <groupId>org.elasticsearch</groupId>
> > > > > > > > > <artifactId>elasticsearch</artifactId>
> > > > > > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > > > > > <exclusions>
> > > > > > > > > <exclusion>
> > > > > > > > > <groupId>com.sun.jmx</groupId>
> > > > > > > > > <artifactId>jmxri</artifactId>
> > > > > > > > > </exclusion>
> > > > > > > > > <exclusion>
> > > > > > > > > <groupId>com.sun.jdmk</groupId>
> > > > > > > > > <artifactId>jmxtools</artifactId>
> > > > > > > > > </exclusion>
> > > > > > > > > </exclusions>
> > > > > > > > > </dependency>
> > > > > > > > > </dependencies>
> > > > > > > > > 
> > > > > > > > > ```
> > > > > > > > > 
> > > > > > > > > The question is if I elasticsearch will need this jars at some  
> > > > > > > > > point in time. Does anybody have experience developing with ES using maven?  
> > > > > > > > > Are those JARs needed?
> > > > > > > > > 
> > > > > > > > > Regards,  
> > > > > > > > > Lukas
> > > > > > > 
> > > > > > > ## --
> > > > > > > 
> > > > > > > Paul Loy  
> > > > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> > > > > 
> > > > > ## --
> > > > > 
> > > > > Paul Loy  
> > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 3, 2010, 9:12pm UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/11 "2010-05-03T21:12:47Z")

</div>

Sure, go ahead.

On Tue, May 4, 2010 at 12:11 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Should I create a new ticket for this? Actually, it is not a major issue as  
> in normal case I would use public release with modified pom.
> 
> On Mon, May 3, 2010 at 11:03 PM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:
> 
> > Yea, I munge and remove these deps from the pom generated only on the  
> > upload task... . Need to check how to do it in the install phase as well..
> > 
> > On Tue, May 4, 2010 at 12:00 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > 
> > > I did gradle install and it produced elasticsearch-0.7.0-SNAPSHOT.jar  
> > > along with pom file which includes compile time dependency on log4j and  
> > > other libraries (see my second mail for full list). So if I have a maven  
> > > project which has only one dependency, i.e.
> > > 
> > > ```
> > > <groupId>org.elasticsearch</groupId>
> > > <artifactId>elasticsearch</artifactId>
> > > <version>0.7.0-SNAPSHOT</version>
> > > 
> > > ```
> > > 
> > > then I have to exclude  
> > >   
> > > javax.jms  
> > > jms  
> > >   
> > >   
> > > javax.mail  
> > > mail
> > > 
> > > ```
> > > </exclusion>
> > > <exclusion>
> > > <groupId>com.sun.jmx</groupId>
> > > <artifactId>jmxri</artifactId>
> > > </exclusion>
> > > <exclusion>
> > > <groupId>com.sun.jdmk</groupId>
> > > <artifactId>jmxtools</artifactId>
> > > </exclusion>
> > > 
> > > ```
> > > 
> > > explicitly.
> > > 
> > > Regards,  
> > > Lukas
> > > 
> > > On Mon, May 3, 2010 at 10:32 PM, Shay Banon \<  
> > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > 
> > > > If you have a look at the pom (that I linked in the previous mail), then  
> > > > ES does not rely on either slf4j or log4j (it has "yet another" lightweight  
> > > > logging abstarction). Are you using gradle install or are you resolving it  
> > > > from elasticsearch snapshot repo? If you will notice, you will see that  
> > > > elasticsearch only relies on netty and lucene (much work has been done in  
> > > > this version to reduce and jarjar the deps).
> > > > 
> > > > On Mon, May 3, 2010 at 10:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > 
> > > > > Good, but wouldn't it be better to get rid of log4j at all? Can't ES  
> > > > > just use slf4j without log4j bridge?  
> > > > > Lukas
> > > > > 
> > > > > On Mon, May 3, 2010 at 8:58 PM, Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com) wrote:
> > > > > 
> > > > > > yeah, just exclude them:  
> > > > > > [Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net](http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/)
> > > > > > 
> > > > > > On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote:
> > > > > > 
> > > > > > > Yes, they come from log4j
> > > > > > > 
> > > > > > > [INFO] ElasticSearchTest:ElasticSearchTest:war:1.0  
> > > > > > > [INFO] - org.elasticsearch:elasticsearch:jar:0.7.0-SNAPSHOT:compile  
> > > > > > > [INFO] +-  
> > > > > > > org.apache.lucene:lucene-fast-vector-highlighter:jar:3.0.1:compile  
> > > > > > > [INFO] +- org.apache.lucene:lucene-analyzers:jar:3.0.1:compile  
> > > > > > > [INFO] +- log4j:log4j:jar:1.2.15:compile  
> > > > > > > [INFO] | +- javax.mail:mail:jar:1.4:compile  
> > > > > > > [INFO] | | - javax.activation:activation:jar:1.1:compile  
> > > > > > > [INFO] | +- javax.jms:jms:jar:1.1:compile  
> > > > > > > [INFO] | +- com.sun.jdmk:jmxtools:jar:1.2.1:compile  
> > > > > > > [INFO] | - com.sun.jmx:jmxri:jar:1.2.1:compile  
> > > > > > > [INFO] +- jline:jline:jar:0.9.94:compile  
> > > > > > > [INFO] | - junit:junit:jar:3.8.1:compile  
> > > > > > > [INFO] +- org.slf4j:slf4j-api:jar:1.5.11:compile  
> > > > > > > [INFO] +- org.codehaus.jackson:jackson-core-asl:jar:1.5.2:compile  
> > > > > > > [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.11:compile  
> > > > > > > [INFO] +- org.apache.lucene:lucene-core:jar:3.0.1:compile  
> > > > > > > [INFO] +- org.apache.lucene:lucene-queries:jar:3.0.1:compile  
> > > > > > > [INFO] +- org.jboss.netty:netty:jar:3.1.5.GA:compile  
> > > > > > > [INFO] +- joda-time:joda-time:jar:1.6:compile  
> > > > > > > [INFO] - org.yaml:snakeyaml:jar:1.6:compile
> > > > > > > 
> > > > > > > 2010/5/3 Paul Loy [keteracel@gmail.com](mailto:keteracel@gmail.com)
> > > > > > > 
> > > > > > > If it turns out to be coming from log4j you can safely exclude them.
> > > > > > > 
> > > > > > > > On Mon, May 3, 2010 at 5:50 PM, Shay Banon \<  
> > > > > > > > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)\> wrote:
> > > > > > > > 
> > > > > > > > > Can you run the maven dependency tree thingy to see where it is  
> > > > > > > > > coming from? There is no need for it for elasticsarch (here is the pom:  
> > > > > > > > > [http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom](http://oss.sonatype.org/content/repositories/snapshots/org/elasticsearch/elasticsearch/0.7.0-SNAPSHOT/elasticsearch-0.7.0-20100502.221713-10.pom)  
> > > > > > > > > ).
> > > > > > > > > 
> > > > > > > > > On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček \<[lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)
> > > > > > > > > 
> > > > > > > > > > wrote:
> > > > > > > > > 
> > > > > > > > > > Hi,
> > > > > > > > > > 
> > > > > > > > > > I am trying to use elasticsearch in maven project. I built  
> > > > > > > > > > 0.7.0-snapshot locally and installed into local maven repo. But when added  
> > > > > > > > > > this dependency into my maven project then it requires transitive  
> > > > > > > > > > dependencies like com.sun.jdmk:jmxtools:pom:1.2.1 and  
> > > > > > > > > > com.sun.jmx:jmxri:pom:1.2.1. However, these jars are not available in public  
> > > > > > > > > > maven repos due to licencing issues. One easy solution seems to be adding  
> > > > > > > > > > exclusions into pom.xml
> > > > > > > > > > 
> > > > > > > > > > ```
> > > > > > > > > > <dependencies>
> > > > > > > > > > <dependency>
> > > > > > > > > > <groupId>org.elasticsearch</groupId>
> > > > > > > > > > <artifactId>elasticsearch</artifactId>
> > > > > > > > > > <version>0.7.0-SNAPSHOT</version>
> > > > > > > > > > <exclusions>
> > > > > > > > > > <exclusion>
> > > > > > > > > > <groupId>com.sun.jmx</groupId>
> > > > > > > > > > <artifactId>jmxri</artifactId>
> > > > > > > > > > </exclusion>
> > > > > > > > > > <exclusion>
> > > > > > > > > > <groupId>com.sun.jdmk</groupId>
> > > > > > > > > > <artifactId>jmxtools</artifactId>
> > > > > > > > > > </exclusion>
> > > > > > > > > > </exclusions>
> > > > > > > > > > </dependency>
> > > > > > > > > > </dependencies>
> > > > > > > > > > 
> > > > > > > > > > ```
> > > > > > > > > > 
> > > > > > > > > > The question is if I elasticsearch will need this jars at some  
> > > > > > > > > > point in time. Does anybody have experience developing with ES using maven?  
> > > > > > > > > > Are those JARs needed?
> > > > > > > > > > 
> > > > > > > > > > Regards,  
> > > > > > > > > > Lukas
> > > > > > > > 
> > > > > > > > ## --
> > > > > > > > 
> > > > > > > > Paul Loy  
> > > > > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)
> > > > > > 
> > > > > > ## --
> > > > > > 
> > > > > > Paul Loy  
> > > > > > [paul@keteracel.com](mailto:paul@keteracel.com)  
> > > > > > [http://www.keteracel.com/paul](http://www.keteracel.com/paul)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:24am UTC](https://discuss.elastic.co/t/jmxri-and-jmxtools-maven-artefacts/2938/12 "2017-07-06T04:24:17Z")

</div>