activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1129) Client Dependencies
Date Wed, 17 May 2017 15:33:04 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014220#comment-16014220
] 

ASF GitHub Bot commented on ARTEMIS-1129:
-----------------------------------------

Github user Rossi1337 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1272
  
    It is like that. We run an application server that is not OSGI so we have of course already
a version of Apache commons and Google guave, ... they will collide with the version needed
by artemis client and there is no easy way to resolve this. It is not only about adding one
or 4 Jars to the server. It is also about version conflicts. The shading solves this very
elegant.
    A typical JMS application is generic. You normally just add one JMS client jar to the
classpath and you can connect. With this single JAR this looks way cleaner for me. 
    
    Thanks for all your efforts this is highly appreciated I just will check out and give
it a test run.


> Client Dependencies 
> --------------------
>
>                 Key: ARTEMIS-1129
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1129
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.0.0
>            Reporter: Bernd Rosstauscher
>            Assignee: Justin Bertram
>            Priority: Minor
>              Labels: documentation
>
> Currently the documentation is not up to date for the client requirements.
> Section 12. The Client Classpath specifies only the following 
> activemq-core-client.jar, activemq-commons.jar, and netty.jar
> And for JMS the following:
> activemq-jms-client.jar and geronimo-jms_2.0_spec.jar
> If I copy these to my project and try to connect directly via JMS (not via JNDI) I get
at runtime ClassNotFoundExceptions of all kind.
> It seems now you need a lot more JAR files as dependencies. It is not really clear what
else is needed so you will end up to copy the whole Artemis Jars just to make the client connection
work.
> Would it be possible to update the documentation to specify the direct and indirect dependencies
for the client. 
> I have the feeling this is at the moment a little bit out of control as it seems I need
now to include 10 more Jar files or so including the json libraries, org.jboss logging, all
the commons jars and many more?
> Thanks for your great work.
> - Bernd Rosstauscher



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message