[JBoss JIRA] Created: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
6:56 a.m.
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.0.1.SP3, 1.2.0.Beta1
Reporter: Galder Zamarreno
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta2, 1.0.1.SP4
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
6:58 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Galder Zamarreno commented on JBMESSAGING-804:
----------------------------------------------
The current one could be called jboss-messaging-all-client.jar
and the one without external dependencies jboss-messaging-client.jar
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.0.1.SP3, 1.2.0.Beta1
Reporter: Galder Zamarreno
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta2, 1.0.1.SP4
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
3:03 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Ovidiu Feodorov updated JBMESSAGING-804:
----------------------------------------
Fix Version/s: 1.2.0.CR1
(was: 1.2.0.Beta2)
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.0.CR1, 1.0.1.SP4
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
12:25 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Ovidiu Feodorov updated JBMESSAGING-804:
----------------------------------------
Fix Version/s: 1.0.1.SP5
(was: 1.0.1.SP4)
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.0.CR1, 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
5:43 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ 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...
and
http://fisheye.jboss.org/browse/~raw,r=2137/Messaging/branches/Branch_1_0...
(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
11:31 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Ovidiu Feodorov updated JBMESSAGING-804:
----------------------------------------
Fix Version/s: Unscheduled
(was: 1.2.1)
(was: 1.0.1.SP5)
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.0.1.SP3, 1.2.0.Beta1
Reporter: Galder Zamarreno
Assigned To: Ovidiu Feodorov
Fix For: Unscheduled
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
2:25 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Tim Fox updated JBMESSAGING-804:
--------------------------------
Assignee: (was: Ovidiu Feodorov)
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
Fix For: Unscheduled
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
2:35 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ 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
2:35 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-804:
-------------------------------------
We should create a slimmed down jboss-messaging-client.jar that only contains jboss
messaging classes - this is essential to avoid dependency conflicts on the client side
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
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
3:47 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Clebert Suconic reassigned JBMESSAGING-804:
-------------------------------------------
Assignee: Clebert Suconic (was: 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: Clebert Suconic
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
3:49 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-804:
---------------------------------------------
We could use Classpath: annotation on META-INF/Manifest to those external dependencies.
But that will require stop scopping.
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: Clebert Suconic
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
11:47 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=all ]
Clebert Suconic closed JBMESSAGING-804.
---------------------------------------
Resolution: Done
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: Clebert Suconic
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
2:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Andrei Martchouk commented on JBMESSAGING-804:
----------------------------------------------
Tim briefly described what we need. That's correct.
This issue planned for 1.2.0.SP2 according to this jira entry. And it's marked as
"closed". Is the workaround described by Ovidiu the solution?
I'd prefer the Tim's proposal as maintenable solution. Is any work planned for
it?
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: Clebert Suconic
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
4:13 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-804:
-------------------------------------
1.2.0.SP2 will be out next week and will resolve this issue - I suggest you wait for
that.
If you can't wait, then you could put jboss-messaging.jar on your client side as
Ovidiu suggests and manually add the other jars.
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.0.1.SP3, 1.2.0.Beta1
Reporter: Galder Zamarreno
Assigned To: Clebert Suconic
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
4:50 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies
[ http://jira.jboss.com/jira/browse/JBMESSAGING-804?page=comments#action_12... ]
Andrei Martchouk commented on JBMESSAGING-804:
----------------------------------------------
Tanks Tim,
we'll better wait for 1.2.0.SP2, to test the offitial by jboss-team slimmed down
jboss-messaging-client.jar .
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.0.1.SP3, 1.2.0.Beta1
Reporter: Galder Zamarreno
Assigned To: Clebert Suconic
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
6943
days inactive
7048
days old
14 comments
6 participants
participants (6)
-
Andrei Martchouk (JIRA) -
Clebert Suconic (JIRA)
-
Galder Zamarreno (JIRA) -
Ovidiu Feodorov (JIRA)
-
Ovidiu Feodorov (JIRA)
-
Tim Fox (JIRA)