Hi Isuru, comments inline;
On Tue, Sep 28, 2010 at 10:29 AM, Isuru Suriarachchi <[email protected]> wrote: > Hi Pradeep, > > Please see my comments inline.. > > On Tue, Sep 28, 2010 at 9:59 AM, Pradeep Fernando <[email protected]> wrote: >> >> Hi devs, >> >> I went through the orbit bundles & collected some data regarding the >> existing bundles. There I checked the versions in the trunk, weather >> the versions has changed since the carbon 3.0.0 release, weather the >> artifacts are available in the maven repo. >> According to my observations the following orbit bundles haven't >> undergone any significant changes, apart from adding licenses, etc . >> So these are strong candidates for graduation. > > +1. These modules can be graduated for sure.. > >> >> bcel.wso2 >> smackx.wso2 >> xml.apis.wso2 >> jaxbri.wso2 >> sun-xacml.wso2 >> commons.beanutils.wso2 >> commons.dbcp.wso2 >> com.lowagie.wso2 >> cindy.wso2 >> jcommon.wso2 >> httpcore.nio.wso2 >> neethi.wso2 >> woden.wso2 >> joscar-client.wso2 >> tiles.wso2 >> commons.httpclient.wso2 >> commons-digester.wso2 >> jmdns.wso2 >> jibx.wso2 >> geronimo.saaj.1.3.spec.wso2 >> hibernate.wso2 >> bsh.wso2 >> wsdl-validator.wso2 >> saxon-bps.wso2 >> poi.wso2 >> joscar-protocol.wso2 >> geronimo.j2ee.connector.1.5.spec.wso2 >> google.common.collect.wso2 >> jdom.wso2 >> jfreechart.wso2 >> stax.impl.wso2 >> jakarta.taglibs.wso2 >> mvel2.wso2 >> batik.wso2 >> opensaml.wso2 >> ajaxtags.wso2 >> commons.primitives.wso2 >> quartz.wso2 >> jxl.wso2 >> geronimo.transaction.wso2 >> gdata.core.wso2 >> joscar-common.wso2 >> commons.net.wso2 >> ehcache.wso2 >> ant.wso2 >> spring.framework.wso2 >> poi-scratchpad.wso2 >> joda-time.wso2 >> commons.pool.wso2 >> js.wso2 >> xmlbeans.wso2 >> socks.wso2 >> xalan.wso2 >> commons.fileupload.wso2 >> geronimo.jta.1.1.spec.wso2 >> jettison.wso2 >> jasper-jdt.wso2 >> tribes.wso2 >> kaptcha.wso2 >> cglib.wso2 >> httpcore.wso2 >> opencsv.wso2 >> jasperreports.wso2 >> log4j.wso2 >> commons.io.wso2 >> derby.wso2 >> persistence.api.wso2 >> poi-ooxml.wso2 >> jaxws.wso2 >> gdata.spreadsheet.wso2 >> hapi.wso2 >> commons.codec.wso2 >> JCIFS library >> axion.wso2 >> asm.wso2 >> geronimo.connector.wso2 >> annogen.wso2 >> openjpa.wso2 >> serp.wso2 >> wsdl4j.wso2 >> commons.collections.wso2 >> tranql.connector.wso2 >> WSO2 Solr Client >> geronimo.ejb.2.1.spec.wso2 >> hsqldb.wso2 >> geronimo.spec.javamail.wso2 >> compass.project.wso2 >> abdera-extensions.wso2 >> jml.wso2 >> commons.lang.wso2 >> geronimo.jms.1.1.spec.wso2 >> JSch ssh >> xalan-ode.wso2 >> rome.wso2 >> opensaml2.wso2 >> abdera.wso2 >> backport.util.concurrent.wso2 >> antlr.wso2 >> smack.wso2 >> geronimo.kernel.wso2 >> janino.wso2 >> wsdl4j.wso2 >> WSO2 Carbon - Orbit - Commons VFS >> jsr94.wso2 >> org.antlr.wso2 >> geronimo.spec.jms.wso2 >> >> >> Apart from above listed bundles , the following bundles have undergone >> version changes since the 3.0.0 branch. But other than that they are >> not showing any major development efforts. Most of the time new lib >> versions has been introduced to the bundle. IMO we can graduate these >> bundles as well. > > Do you mean that these bundles wrap different versions of the original > library? If that is the case, you can't graduate these. > Or else, if you mean that the version given for the orbit bundle is changed, > (ex: "." and "-" changes) you have to check the reasons behind it. If you > decide to use the older version by graduating that particular bundle, you > have to fix it's version in core, components etc as well.. Yes, both the above scenarios are visible in the orbit bundles. For an example in the savan-core bundle the savan lib version is changed from 1.0.0.wso2v2 to 1.0.0.wso2v3. Another example is the drools bundle, where it has changed its lib from version 5.0.1 to 5.1.1 There are scenarios where version changes are done to the bundle without changing the lib it wraps. In Xerces they have used 2.8.1.wso2v2 bundle where as in the trunk they are using 2.8.1.wso2v1. Still both these bundles use the same xerces impl -> 2.8.1 > >> >> xkms.wso2 >> WSO2 H2 Osgi Console Service >> WSO2 Carbon - Eventing Savan >> drools.wso2 >> wss4j.wso2 >> axis.wso2 >> jruby.wso2 >> smooks.wso2 >> htmlcleaner.wso2 >> webharvest.wso2 >> bsf.wso2 >> oauth core >> jruby.wso2 >> xmlschema.wso2 >> js.wso2 >> xerces >> openid4java >> >> >> >> The following bundles showing some rapid changes & over the period & >> bundles like axis2 uses snapshot versions of the jars. So we cant >> graduate these bundles i guess. >> >> >> axis2-jibx >> axis2-jaxbri >> rampart-trust >> axis2-json >> axis2 >> rampart-core >> axiom.wso2 >> ode >> rampart-policy >> shindig // not using the snapshots but, frequent changes >> >> >> at first observation , it seemed like saxon-bps falls in to the above >> category. But according to Milinda , it is a patched version to cater >> BPS specific requirements. As Milinda said we can get rid of the >> saxon-bps bundle if we can put latest saxon libs in to saxon bundle. >> After that it is a possible graduation candiadate. >> >> In conclusion, most of the orbit bundles are good for graduation since >> they are wrappers for third party libs. My note on the orbit bundles >> can be found at [1]. please ignore any cell - colorings since they are >> only for my personnel reference. >> >> Suggestions & feedbacks are appreciated. :) > > When you do this, please make sure that it is easy to add back a graduated > module into the build and do the necessary changes. > > Thanks, > ~Isuru > >> >> [1] >> https://spreadsheets.google.com/pub?key=0Aj93FnJ8mzOrdDZ4MGdaODVwQnNjOHl1LTFWWmhmU0E&hl=en&single=true&gid=0&output=html >> >> cheers, >> Pradeep >> >> -- >> Pradeep Fernando >> Software Engineer >> WSO2 Inc. >> blog: http://pradeepfernando.blogspot.com/ >> m: +94776603662 >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > -- > Isuru Suriarachchi > Technical Lead & Product Manager, WSO2 Web Services Application Server > WSO2 Inc. http://wso2.com > email : [email protected] > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Pradeep Fernando Software Engineer WSO2 Inc; blog: http://pradeepfernando.blogspot.com/ m: +94776603662 _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
