Hi Kernel Team,

There are other issues if we move to carbon-commons 4.5.0, one being DSS
feature installation in ESB 4.9.0 will fail, because they are using commons
4.4.7 (with import range [4.4.0,4.5.0)) and our import range will be
[4.5.0,5.0.0).

Other issue would be, we have tested(DSS, DAS) both with existing versions,
(commons 4.4.7 and carbon-mutitenancy 4.4.3) and if we are to move to
commons 4.5.1 version, we have to migrate to multitenancy newer version as
well, As we are in RC state (Both DAS and DSS) that would be bit risky. It
will be great if we can have commons 4.4.8 release.

[1] is the critical fix that we will need in that release. There is another
UI improvement (which was refused to merge because of API changes) [2] as
well. It will be great if we can have commons 4.4.8 release with those
fixes.

[1] -
https://github.com/wso2/carbon-commons/commit/aa844c5616a92d5843e69693154d09d282214d74
[2] - https://github.com/wso2/carbon-commons/pull/172

Thanks,

On Wed, Oct 21, 2015 at 12:59 PM, Anjana Fernando <[email protected]> wrote:

> +1, yeah, let's go with a 4.4.x release.
>
> Cheers,
> Anjana.
>
> On Wed, Oct 21, 2015 at 12:08 PM, Rajith Vitharana <[email protected]>
> wrote:
>
>> Hi,
>>
>> I guess we have to go with commons 4.4.x rather than 4.5.1, because I
>> have tried to build with commons 4.5.0 and it wasn't successful, throw
>> below error
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Tenant Common Composite Feature 4.4.3
>> (org.wso2.carbon.tenant.common.feature.group 4.4.3)
>>  Missing requirement: WSO2 Tenant Common Composite Feature 4.4.3
>> (org.wso2.carbon.tenant.common.feature.group 4.4.3) requires
>> 'org.wso2.carbon.tenant.mgt.common.feature.group [4.4.4,4.5.0)' but it
>> could not be found
>> Application failed, log file location:
>> /home/rajith/Wso2/mavenRepo/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1445409020170.log
>>
>> seems carbon tenant common composite feature 4.4.3 (latest released
>> version ) required a commons version below 4.5.0, So if we are going to go
>> with commons 4.5.1, we may have to get a release of carbon-multitenancy as
>> well, So shall we go ahead with commons 4.4.x?
>>
>> Below are the new fixes that needs to be in 4.4.x
>>
>> [1] -
>> https://github.com/wso2/carbon-commons/commit/3290aa0a9b41c6fc1804b6e383a1540e9e888a2a
>> This is a bug fix
>> [2] -
>> https://github.com/wso2/carbon-commons/commit/0b9f08299b13348d11cf0bc5d92da9c492c782f5
>> This is just indentation
>> [3] - https://github.com/wso2/carbon-commons/pull/172
>> This is a UI improvement done for jira [4]. It has only client side (UI)
>> fixes and only DSS uses them
>> [4] - https://wso2.org/jira/browse/DS-1034
>>
>> Will we be able to get a commons 4.4.x out with those fixes?
>>
>> Thanks,
>>
>>
>> On Wed, Oct 21, 2015 at 2:09 AM, Anjana Fernando <[email protected]> wrote:
>>
>>> Hi Sameera / KasunG,
>>>
>>> We are doing RC releases for DAS and DSS today (21'st), and we have
>>> several fixes done for Carbon Commons, among them, a blocker [1] being
>>> fixed for DAS. Can we please get a patch release done for Carbon Commons
>>> today, since we have critical deadlines for these products, and their RCs
>>> must go out today, thus we need these fixes as well.
>>>
>>> [1] https://wso2.org/jira/browse/CCOMMONS-2
>>>
>>> Cheers,
>>> Anjana.
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Rajith Vitharana
>>
>> Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94715883223
>> Blog : http://lankavitharana.blogspot.com/
>>
>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
Rajith Vitharana

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94715883223
Blog : http://lankavitharana.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to