[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies

[Ovidiu Feodorov (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]

Ovidiu Feodorov updated JBMESSAGING-804:
----------------------------------------

    Fix Version/s: 1.2.1
                       (was: 1.2.0.CR1)

No answer since my 2/9/2007 reply on the case.  Pushing to 1.2.1. This case will be most likely closed with "Won't fix". This is why:

JBoss Messaging has an extensive tree of dependencies, and we thought we're actually doing the user a great service by bundling all these dependencies together so no wrong versions inadvertently get in the class path. If, for example, the log4j.jar bundled with the release causes problems for being too old, you could just simply build your client-side class path so a newer version of log4j.jar precedes jboss-messaging-client.jar in that class path.

This approach may work, but is not guaranteed to work, because we did not run the full test suite with any other log4j.jar version except the one we bundle with the release. Our tested dependency is currently http://repository.jboss.com/apache-log4j/1.2.8/component-info.xml

If bare messaging client-side library is needed, jboss-messaging.jar library that ships with the release can be used for that. It is available inside jboss-messaging-scoped.sar, which is included with the release bundle and also on-line at http://repository.jboss.com/jboss/messaging. Please be aware that in this case you will need to build the client-side dependency tree all by yourself. For a complete list of client-side dependencies, please consult http://fisheye.jboss.org/browse/~raw,r=2229/Messaging/branches/Branch_1_0_1_SP/build-messaging.xml and http://fisheye.jboss.org/browse/~raw,r=2137/Messaging/branches/Branch_1_0_1_SP/build-thirdparty.xml (this is valid for Branch 1.0.1.SP)



> Provide a clean jboss-messaging-client.jar without containing external dependencies
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-804
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-804
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Build System
>    Affects Versions: 1.2.0.Beta1, 1.0.1.SP3
>            Reporter: Galder Zamarreno
>         Assigned To: Ovidiu Feodorov
>             Fix For: 1.2.1, 1.0.1.SP5
>
>
> We've installed JBoss messaging instead of JBossMQ and updated our application to connect to this. 
> We have to include jboss-messaging-client.jar to be able to use it, but now the following problem arises:
> jboss-messaging-client.jar has log4j classes in it, which are of an old version. Therefore, our .war 
> cannot deploy because it uses methods of log4j of the newer version (e.g. Logger.isTraceEnabled()).
> To your approach of patching jboss-messaging-client.jar: maybe we'll try it, but I'm afraid it includes 
> more classes that may clash with our system... What we need is a clean jboss-messaging-client.jar file, 
> without external dependencies, but I don't want to build it myself as it makes maintaining our JBoss 
> setup very hard.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira