-
1. Re: Continue to bundle up Remoting classes in jboss-messagin
clebert.suconic Apr 18, 2007 11:00 AM (in response to jay.howell)I have seen so many other issues on having these jars on jbossall-client.jar also.
I would like also to remove jboss-remoting.jar from jbossall-client.jar. Scott/Dimitris would have to take the decision on doing it.
Tom Elrod added this to jbossall-client.jar and as I remember the only reason was to make Customer's life easier... and as this is making their lifes more difficult we should stop doing it.
Scott/Dimitris.. .what you guys think?
Clebert -
2. Re: Continue to bundle up Remoting classes in jboss-messagin
starksm64 Apr 18, 2007 12:43 PM (in response to jay.howell)In terms of evolution of an existing install, there is nothing good about the jbossall-client.jar. If it exists it really should be an empty jar that only includes a manifest classpath pointing to the jars that should be on a client classpath.
-
3. Re: Continue to bundle up Remoting classes in jboss-messagin
timfox Apr 18, 2007 1:13 PM (in response to jay.howell)We should definitely provide a jboss-messaging-client.jar which contains the jboss messaging classes and nothing else (or maybe just a few other jars that are highly unlikely to change - TBD)
I have created a JIRA task for it:
http://jira.jboss.org/jira/browse/JBMESSAGING-940 -
4. Re: Continue to bundle up Remoting classes in jboss-messagin
dimitris Apr 20, 2007 5:50 AM (in response to jay.howell)recorded it here:
http://jira.jboss.com/jira/browse/JBAS-4355