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

[Tim Fox (JIRA)]

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

Tim Fox updated JBMESSAGING-804:
--------------------------------

    Fix Version/s: 1.2.0.SP2
                       (was: Unscheduled)
         Assignee: Tim Fox

> 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: Tim Fox
>             Fix For: 1.2.0.SP2
>
>
> 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