Jmxri and jmxtools Maven artefacts

Lukas_Vlcek1 · May 3, 2010, 3:33pm

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

kimchy · May 3, 2010, 4:50pm

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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček 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 · May 3, 2010, 6:19pm

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.comwrote:

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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček 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
http://www.keteracel.com/paul

Lukas_Vlcek1 · May 3, 2010, 6:46pm

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

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.comwrote:
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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul

Paul_Loy · May 3, 2010, 6:58pm

yeah, just exclude them:

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček 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

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.comwrote:
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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul

--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

Lukas_Vlcek1 · May 3, 2010, 7:03pm

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 wrote:

yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček 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

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

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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

kimchy · May 3, 2010, 8:32pm

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 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 wrote:
yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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

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> 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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

Lukas_Vlcek1 · May 3, 2010, 9:00pm

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.comwrote:

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.comwrote:
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 wrote:
yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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

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> 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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

kimchy · May 3, 2010, 9:03pm

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 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.comwrote:
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.comwrote:
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 wrote:
yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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

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> 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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

Lukas_Vlcek1 · May 3, 2010, 9:11pm

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.comwrote:

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.comwrote:
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

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.comwrote:
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 wrote:
yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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

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> 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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul

kimchy · May 3, 2010, 9:12pm

Sure, go ahead.

On Tue, May 4, 2010 at 12:11 AM, Lukáš Vlček 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.comwrote:
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.comwrote:
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> 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.comwrote:
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 wrote:
yeah, just exclude them:
Resolving log4j 1.2.15 dependency problems in Maven using exclusions » unitstep.net

On Mon, May 3, 2010 at 7:46 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:
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

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> 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
).

On Mon, May 3, 2010 at 6:33 PM, Lukáš Vlček <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
http://www.keteracel.com/paul
--

Paul Loy
paul@keteracel.com
http://www.keteracel.com/paul