[Carbon-dev] We may need to branch Axis2 for next carbon (or component level) release ?

There's a issue regarding concurrent modification exception when ESB startup[1]..We believe this is due to a issue in Axis2 Deployment Engine , ie:-deploymentMap not being thread safe..To do this change for next release we meed to branch Axis2..is it possible to do this? Regards, Udayanga

Re: [Carbon-dev] We may need to branch Axis2 for next carbon (or component level) release ?

Yes. But I'm afraid if you do that, you may not be able to release the dependent components separately. It is possible to fix this in the 3.2.0 branch. On Tue, Jun 21, 2011 at 11:30 AM, Udayanga Wickramasinghe udaya...@wso2.com wrote: There's a issue regarding concurrent modification exception

Re: [Carbon-dev] We may need to branch Axis2 for next carbon (or component level) release ?

The bug is in the 3.2.0 axis2 branch. If we fix it we have to create a new version of axis2 for the 3.2.1 release. Shall we do it or just leave this bug as it is for the 3.2.1 release? Thanks, Supun.. On Tue, Jun 21, 2011 at 12:10 PM, Afkham Azeez az...@wso2.com wrote: Yes. But I'm afraid if

Re: [Carbon-dev] We may need to branch Axis2 for next carbon (or component level) release ?

This is not a major issue. There is no need to change Axis2 in 3.2.0. On Tue, Jun 21, 2011 at 2:26 PM, Supun Kamburugamuva su...@wso2.com wrote: The bug is in the 3.2.0 axis2 branch. If we fix it we ha ve to create a new version of axis2 for the 3.2.1 release. Shall we do it or just leave