I believe this is an old issue, as I remember already seeing some thread about this some time ago. (2 years maybe... man.. that seems yesterday :-) ) But now that JBossMessaging is part of JBoss 5 Betas, and JBoss EAP 4.3, this is becoming more relevant for our users. Since JBoss Messaging 1.4 is using AOP on both client and server, users can't just use jboss-allclient.jar on their classpath. They also have to include all the AOP dependencies (like javassist, aop itself and trove), so the jbossall-client.jar is broken on the user's experience: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129155 So, can we add AOP and dependencies to jbossall-client.jar. Or better.... can't we just deliver an empty jar referencing the other jars required on the client? I tried to do that also on the EAP 4.3, but production guys told me that the CLASSPATH metainf thing is being deprecated, so we were stuck with the old way of doing it. Maybe we need to just add those class there, or.. is there any way to do it? I have also created a Dev forum at JBoss Messaging Developer's: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129288 If nobody thinks there is an issue, I will just fix that adding the AOP dependencies into jbossall-client.jar, for next JBoss 5 and EAP 4.3 releases. Clebert _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

> My vote is that jbossall-client.jar is just dropped. Its just duplicate > bloat that is wrong depending on what features your using. +1... for JBoss 5.

But for JBoss AS 4.3.... we have users still using it.

Scott M Stark wrote: > My vote is that jbossall-client.jar is just dropped. Its just duplicate > bloat that is wrong depending on what features your using. > > Clebert Suconic wrote: >> I believe this is an old issue, as I remember already seeing some thread >> about this some time ago. (2 years maybe... man.. that seems yesterday >> :-) ) >> >> But now that JBossMessaging is part of JBoss 5 Betas, and JBoss EAP 4.3, >> this is becoming more relevant for our users. >> >> Since JBoss Messaging 1.4 is using AOP on both client and server, users >> can't just use jboss-allclient.jar on their classpath. They also have to >> include all the AOP dependencies (like javassist, aop itself and trove), >> so the jbossall-client.jar is broken on the user's experience: >> >> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129155 >> >> >> So, can we add AOP and dependencies to jbossall-client.jar. Or >> better.... can't we just deliver an empty jar referencing the other jars >> required on the client? >> >> >> I tried to do that also on the EAP 4.3, but production guys told me that >> the CLASSPATH metainf thing is being deprecated, so we were stuck with >> the old way of doing it. Maybe we need to just add those class there, >> or.. is there any way to do it? >> >> I have also created a Dev forum at JBoss Messaging Developer's: >> >> >> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129288 >> >> >> If nobody thinks there is an issue, I will just fix that adding the AOP >> dependencies into jbossall-client.jar, for next JBoss 5 and EAP 4.3 >> releases. >> >> >> Clebert >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

+1 Where does it state that class-path is deprecated?

+1 Where does it state that class-path is deprecated? Carlo Tim Fox wrote: > > > Clebert Suconic wrote: >> > My vote is that jbossall-client.jar is just dropped. Its just >> duplicate >> > bloat that is wrong depending on what features your using. >> >> +1... for JBoss 5. > > +1 > >> >> >> But for JBoss AS 4.3.... we have users still using it. > > How about we expand jboss-aop-client.jar to include the missing jars? > (aop, trove + javassist) > >> >> Scott M Stark wrote: >>> My vote is that jbossall-client.jar is just dropped. Its just duplicate >>> bloat that is wrong depending on what features your using. >>> >>> Clebert Suconic wrote: >>>> I believe this is an old issue, as I remember already seeing some >>>> thread >>>> about this some time ago. (2 years maybe... man.. that seems yesterday >>>> :-) ) >>>> >>>> But now that JBossMessaging is part of JBoss 5 Betas, and JBoss EAP >>>> 4.3, >>>> this is becoming more relevant for our users. >>>> >>>> Since JBoss Messaging 1.4 is using AOP on both client and server, >>>> users >>>> can't just use jboss-allclient.jar on their classpath. They also >>>> have to >>>> include all the AOP dependencies (like javassist, aop itself and >>>> trove), >>>> so the jbossall-client.jar is broken on the user's experience: >>>> >>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129155 >>>> >>>> >>>> So, can we add AOP and dependencies to jbossall-client.jar. Or >>>> better.... can't we just deliver an empty jar referencing the other >>>> jars >>>> required on the client? >>>> >>>> >>>> I tried to do that also on the EAP 4.3, but production guys told me >>>> that >>>> the CLASSPATH metainf thing is being deprecated, so we were stuck with >>>> the old way of doing it. Maybe we need to just add those class there, >>>> or.. is there any way to do it? >>>> >>>> I have also created a Dev forum at JBoss Messaging Developer's: >>>> >>>> >>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129288 >>>> >>>> >>>> If nobody thinks there is an issue, I will just fix that adding the >>>> AOP >>>> dependencies into jbossall-client.jar, for next JBoss 5 and EAP 4.3 >>>> releases. >>>> >>>> >>>> Clebert >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

My vote is that jbossall-client.jar is just dropped. Its just duplicate bloat that is wrong depending on what features your using.

Its beyond that. We said we could not put non-lgpl content into this, so features like logging need other jars. It also complicates patching. The best alternative would be to have Class-Path only jar(s) to replace it. Adrian Brock wrote: > On Thu, 2008-02-07 at 13:18 -0800, Scott M Stark wrote: >> My vote is that jbossall-client.jar is just dropped. Its just duplicate >> bloat that is wrong depending on what features your using. > It's wrong because we don't test against it. > > If we fixed the testsuite to only jbossall-client.jar in the classpath > then we'd quickly spot when it wasn't up-to-date. _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I reverted Alexey's last change as it's breaking the build. http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x/1012... You've probably compiled with jdk16?