Hi Thilina; 1) In my experience most of the users simply does not selectivly add remove jars. You might know axis1 had a jar called axis-ant.jar .. which had ant tasks. There is no reason to add it to a classpath, unless you invoke a ant task. However most of the users have it in the classpath.
2) Other side of the story is it is not very simple to figure out which ones you need and whcih ones you do not. Belive me if you are not a developer, names help much at all 3) Look at the size of the jars $ du -h *.jar|grep axis2 136K axis2-adb-1.1-SNAPSHOT.jar 104K axis2-adb-codegen-1.1-SNAPSHOT.jar 172K axis2-codegen-1.1-SNAPSHOT.jar 56K axis2-java2wsdl-1.1-SNAPSHOT.jar 8.0K axis2-jaxbri-1.1-SNAPSHOT.jar 24K axis2-jibx-1.1-SNAPSHOT.jar 656K axis2-kernel-1.1-SNAPSHOT.jar 80K axis2-saaj-1.1-SNAPSHOT.jar 28K axis2-soapmonitor-1.1-SNAPSHOT.jar 8.0K axis2-spring-1.1-SNAPSHOT.jar 8.0K axis2-tools-1.1-SNAPSHOT.jar 16K axis2-xmlbeans-1.1-SNAPSHOT.jar I do not think tools, xmlbeans, sping do any harm at all by merging to main jar. Even others, it is small prize to make life easier for 90% use case. All jars are 9.3 MB. Most of the jars we argue about are about or less than 100k which is about 1/100 of the distribution. I see nothing wrong in put everything in one jar. And if somebody has real need, he could always take it from the maven repo. Dims I belive 1.1 is good place to fix this. My feeling is it is best to do it in 1.1 rather than post 1.1. It has nothing to do with features, so we have no fear in breaking something. Thanks Srinath On 10/26/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Hi, > So I propose that we name the jars according to distro. Say like > axis2-min-1.1.jar and axis2-std-1.1.jar. Aha... There's another thread going on proposing to kill the min-dist.. So we can be better off with axis2-1.1.jar Said that I'm 0+ on this... Even though we do this, there will be a considerable number of jars remaining.. On the other hand I feel that users will feel much more powered when they get separate jars for separate modules, so that they can drop and choose whatever they need.. I know it's possible to pull them off from the maven repo.. But life would be much easier when they arrive separately with the axis2-bin distro.... Thanks, Thilina > > Ajith > > On 10/25/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > Srinath Perera wrote: > > > Hi All; > > > > > > For 1.1 are we planing to put all Axis2 jars on one axis2 jar. (When I > > > purposed, Eran agreed .. no body opposed ...). ? > > > > > > We could keep all other jars in the maven repositories, but for the > > > relase we can make a one jar out of all axis2 classes. > > > > +1 ( again :) ) > > > > > > > > It is best if we can do same for Axiom as well > > > > Well, I do not agree with this. People some times doesn't need DOM jar > > at all. > > > > Anyway, there was a request from Abdera team to take out SOAP specific > > stuff from axiom api and axiom impl. We need to discuss that also in > > commons-dev. Waiting till Axis2 1.1 hit the road. > > > > -- Chinthaka > > > > > > > > > > > -- > Ajith Ranabahu > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- ============================ Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
