Hi all,

I was working on upgrading shindig for last few weeks; and have almost
completed the task. However I have not committed any of the changes to the
trunk yet due to few concerns. The latest shindig made me to upgrade some of
the orbit bundles [1] and that might effect their usages in other
components. Ideally I assume the libraries are backward compatible and we
wont run into any issues. Another concern is that in-order to upgrade some
of these bundles I will have to demote them from the current graduate state.
So those bundles which were graduated will be taken back to the trunk/orbit.

If anybody have concerns over these bundle upgrades please do shout.

[1] Bundle List :

   *Bundle* *Graduated* *Current version* *Upgraded version*
commons-fileupload Y 1.2 1.2.2  google-collect (Google-collections) Y Locally
maintained 1.0 Completely removing and replacing by Guava;
http://code.google.com/p/google-collections/  commons-codec Y 1.3 1.4
shindig N r910768 (shindig 1.1) r1158449 (Shindig 3.0 Beta)  guice N v2.0
v3.0  json N 20070829 20090211  commons-lang N 2.3 2.6  guava N r05 r08
httpclient N 4.1-alpha1 4.1

-- 
*Thanks & Regards,

Nuwan Bandara
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

http://nuwan.bandara.co
*
<http://www.nuwanbando.com/>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to