-
1. Re: cglib,asm not available in client dir
starksm64 Apr 13, 2006 8:07 PM (in response to thomas.diesler)And my view is that this dependency should never have crept in. javassist is the dominate bytecode maninpulation framework and hibernate upated to support it. If anything, jbossws-1.0.0 needs to be delayed until this dependency is removed in favor of the already existing javassist dependency.
-
2. Re: cglib,asm not available in client dir
thomas.diesler Apr 13, 2006 8:15 PM (in response to thomas.diesler)Ok, that can be done.
<path id="client.classpath"> <fileset dir="${jboss.home}/client"> <include name="jbossall-client.jar"/> <include name="jbossws14-client.jar"/> <include name="jbossws-client.jar"/> <include name="commons-logging.jar"/> <include name="jboss-backport-concurrent.jar"/> <include name="jbossretro-rt.jar"/> <include name="activation.jar"/> <include name="log4j.jar"/> <include name="mail.jar"/> </fileset> <fileset dir="${jboss.home}/server/${jboss.server}/lib" includes="cglib-*.jar"> <include name="asm.jar"/> </fileset> </path>
Can we move these to jbossall-client.jar<include name="commons-logging.jar"/> <include name="jboss-backport-concurrent.jar"/> <include name="jbossretro-rt.jar"/>
-
3. Re: cglib,asm not available in client dir
thomas.diesler Apr 13, 2006 8:17 PM (in response to thomas.diesler)Remove dependency on cglib
http://jira.jboss.com/jira/browse/JBWS-842 -
4. Re: cglib,asm not available in client dir
thomas.diesler Apr 13, 2006 8:18 PM (in response to thomas.diesler)commons-logging should probably not be in jbossall-client.jar, but how about the jbossretro jars?
-
5. Re: cglib,asm not available in client dir
starksm64 Apr 13, 2006 11:31 PM (in response to thomas.diesler)This would make jbossall-client.jar dependent on javassist and since we include jbossall-client.jar both the java5/java1.4.x profiles, we would have to include javassist in both. I suppose that is not a problem and that eventually we would need javassist for ejb3/aop on the client container anyway.
-
6. Re: cglib,asm not available in client dir
jason.greene Apr 19, 2006 12:59 AM (in response to thomas.diesler)This is done.
-
7. Re: cglib,asm not available in client dir
thomas.diesler Apr 20, 2006 4:42 PM (in response to thomas.diesler)Currently jboss-backport-concurrent.jar and concurrent.jar cannot be included in jbossall-client.jar at the same time, because when unzipping the jars there is no difference between 'EDU' and 'edu' on a WinXP system.
I suggest concurrent.jar should be backported to org.jboss.edu.... -
8. Re: cglib,asm not available in client dir
ryan.campbell Apr 25, 2006 6:42 PM (in response to thomas.diesler)Could we use zipfilesets to aggregate the jars instead? This would make the build more incremental by getting rid of the delete/unjar/jar process and just have one jar task with zipfilesets for each jar file. Unless we are doing it this way for some reason.
This way we wouldn't have to rename the package, and the build would go faster.