Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (athena.apache.org: domain of aleks.dimitrov@gmail.com
 designates 209.85.212.177 as permitted sender)
From: Aleksandar Dimitrov <aleks.dimitrov@gmail.com>
Date: Wed, 10 Dec 2014 23:57:39 +0100
To: user@uima.apache.org
Subject: uima-as-activemq problematic dependency on activemq-all
Message-ID: <20141210225739.GD3396@minsk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA"
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)

--neYutvxvOLaeuPCA
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

While the download instructions of ActiveMq[0] suggest including activemq-a=
ll in
your pom.xml, this is actually a bad idea. See the discussion here on ticket
AMQ-5009 [1]. The .jar is built using the Maven shade plugin, which directly
dumps libraries in the classpath, without allowing usage of the Maven <excl=
ude>
directive.

If a project pulls in activemq-all, it now *has* to use the implementations=
 of
all its libraries compiled into the jar, and cannot depend on them directly.
This is clearly not a good idea, and will indeed cause problems =E2=80=94 f=
or example
with SLF4J. If I write an application that depends on SLF4J for logging, and
uima-as-scaleout, the transitively pulled in activemq-all will cause a clas=
spath
conflict for the SLF4J library. This problem is recorded in UIMA-3633 [2], =
but
the proposed fix does not work (as of version uima-as-activemq 2.6.0.) Nor
does it seem to be the appropriate fix, since depending on the Maven-shaded=
 jar
could cause problems not only with SLF4J.

A better solution would be to depend on the activemq components separately.=
 My
current workaround in my application's pom.xml reads like this:

=E2=80=A6
<dependencies>
  =E2=80=A6
  <dependency>
    <groupId>org.apache.uima</groupId>
    <artifactId>uimaj-as-activemq</artifactId>
    <version>2.6.0</version>
    <exclusions>
      <exclusion>
        <groupId>org.apache.activemq</groupId>
        <artifactId>activemq-all</artifactId>
      </exclusion>
    </exclusions>
  </dependency>
  <dependency>
    <groupId>org.apache.activemq</groupId>
    <artifactId>activemq-core</artifactId>
    <version>5.7.0</version>
  </dependency>
  =E2=80=A6
</dependencies>

Note that I probably will need to include more than just activemq-core.
While this *works* it should be clear, that it is not a very satisfactory
solution. I propose pre-empting the decision on AMQ-5009, and switching away
=66rom the dependency on activemq-all, which in any case should not be depe=
nded
upon because of the way it dumps all _its_ dependencies in the classpath.

Regards,
Aleks

PS: I'm not subscribed to the dev-list, so if this is supposed to go there,=
 I
could cross post it later, or you can feel free to cross-post it there.

---

[0] http://activemq.apache.org/activemq-5100-release.html (look for "Getting
the Binaries using Maven 2")
[1] https://issues.apache.org/jira/browse/AMQ-5009
[2] https://issues.apache.org/jira/browse/UIMA-3633

--neYutvxvOLaeuPCA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUiM/jAAoJEA4fDuQpC7qF5YEP/R3ZnseDEvr3zqv/S/Nu7atr
0yC0lRDlqHcLkts738CldHqvqkrXpBXzkPyTL/PyNuyDHT9ttUxtirgHD+21dmyJ
RGkPrPEz4QpJcnCJFIZD5arYVZiCU9dtmVmTT/Z7c6OcTnrq3ETfKjDm1EafIUcJ
Jeo1iiv3FZoQo9KMiC3PUs4o6F70KCyxQ+vLdZByRlwc8wbabBHvu6BJhWK3S6e1
Dgeo9fWvmm25WtZ4K0NAcCj6Kdc8n5r1TVH/+48G8wp6k9sPfDggQr2T8S05p9YP
Bl2TUFaTAhT5yRcrIBv9XbsD4AkEmdLaurGJUzAriMPF2Ue1kkO1F75ayXAj4Qbl
yAVwBlLkpUkWvGejJw5u72grk9qCfxMbDhgO7rp73VnWL4UIw5jS+ISm8SZRSUPU
r4P9ty7Mmb0WfZLHwG0cRygpAc8kbJ/IhCZ8YB6aHH4MlrPSJmwZWjoCdUSTLovb
sqUCIkAoLkJnDhfJKui534kcJ+gVXYbiYoAeVB5Vy9SXvrHumKMKTASf7KiNEdVb
8XVtEDCQofmdtklgymYKskHcPq30Lk3Gl1+OCL2YjIKVGOAkpQr/5gG8t8Nu/7ns
vNuSuev5GMvRm6tXJns1sAVWokUFrAQOqvliNFFmuFw4F95CvtH+lH96RPut+dqc
goFs2VSG5Kf4IKyoIc3J
=uSqb
-----END PGP SIGNATURE-----

--neYutvxvOLaeuPCA--