On Fri, Apr 24, 2015 at 3:51 PM, Prabath Abeysekera <[email protected]>
wrote:

> Hi Johann,
>
> I do understand. :) But I'm afraid, this is not a fair excuse for not
> releasing all carbon-identity components with 4.3.3. :) If you guys
> released all components even without 100% stability, then we could have
> simply worked on getting only the bugs (if there happened to be any) fixed
> (worse case), at least by ourselves and continued on the developments. In
> other words, missing a whole bunch of "classes" is unacceptable, even in an
> interim release, let alone the stability of the implementations.
>

This is not a case of a missing class. AFAIR (PrasadT can confirm) this is
a POM issue, and the bundle was not exporting the correct version which was
fixed later.

>
> Further, CDM team too are not planning to release any of our components
> upon 4.3.3, what we're trying to do is simply making the environment ready
> for us to continue all our critical development efforts uninterrupted till
> all other dependent components are released upon 4.4.0. Regarding your
> point on deadlines, yeah I do realize that everyone is on tight deadlines,
> the same applies to us too, which is exactly why we're trying to find a
> resolution to get over this problem. And this is clearly, blocking our
> development efforts which is why I even had to personally come and ask for
> a solution a couple of times, but unfortunately this is not yet solved. I
> hope you understand the current situation and would give us a practical
> solution to this problem :).
>

I don't know how we can patch yet. We haven't got a patching model yet for
git based releases right ?



> Thanks in advance,
>
> Cheers,
> Prabath
>
> On Fri, Apr 24, 2015 at 6:09 AM, Johann Nallathamby <[email protected]>
> wrote:
>
>> Hi Prabath,
>>
>> We are also in the same position because carbon-governance and
>> carbon-store repos are not released. :( So is AS. The solution is to push
>> all the teams to get the repos out ASAP as we discussed in the meeting the
>> other day. Have to scrutinize why its taking so long for other teams to
>> release. No team should be working/releasing on 4.3.x branch AFAIK.
>> Unfortunately we are not in a position to patch 4.3.x branch. We also have
>> only one engineer working on the 4.4.0 based release right now and its not
>> fair on us because we also have deadlines :) .
>>
>> Thanks,
>> Johann.
>>
>> On Fri, Apr 24, 2015 at 3:30 PM, Prabath Abeysekera <[email protected]>
>> wrote:
>>
>>> Hi Johann,
>>>
>>> As I've mentioned in my previous reply, we can't use carbon-identity
>>> 4.3.4 at this point, since there's a bunch of other dependent components
>>> still to be released upon Carbon kernel 4.4.0. Please provide us with a
>>> proper patch upon v4.3.3 before the end of the day today as this is
>>> blocking us big time right now.
>>>
>>> Cheers,
>>> Prabath
>>>
>>> On Fri, Apr 24, 2015 at 12:19 AM, Johann Nallathamby <[email protected]>
>>> wrote:
>>>
>>>> Hi Prabath,
>>>>
>>>> Did you test 4.3.4 ? AFAIK it should work in this version.
>>>>
>>>> Thanks.
>>>>
>>>> On Thu, Apr 23, 2015 at 3:40 PM, Prabath Abeysekera <[email protected]>
>>>> wrote:
>>>>
>>>>> Johann,
>>>>>
>>>>> We've been stuck for weeks because of the issue reported in Harshan's
>>>>> previous reply. As it appears, we wouldn't be able to make MDM components
>>>>> use the latest released version of carbon-identity as the other components
>>>>> that the product depends on won't likely be released at least by the end 
>>>>> of
>>>>> next week. So a patch is urgently needed upon the 4.3.3 components to
>>>>> continue on the MDM development tasks. Please be kind enough to provide on
>>>>> by tomorrow, 24th April.
>>>>>
>>>>> Cheers,
>>>>> Prabath
>>>>>
>>>>>
>>>>> On Mon, Apr 6, 2015 at 11:51 PM, Harshan Liyanage <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi Nuwandi, Johann,
>>>>>>
>>>>>> Thanks for the support.
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Lakshitha Harshan
>>>>>> Software Engineer
>>>>>> Mobile: *+94724423048*
>>>>>> Email: [email protected]
>>>>>> Blog : http://harshanliyanage.blogspot.com/
>>>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>>>>> lean.enterprise.middleware.
>>>>>>
>>>>>> On Tue, Apr 7, 2015 at 9:15 AM, Johann Nallathamby <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> OAuth 4.3.3 in git is found in [1]. But this is not a proper
>>>>>>> released version. When I say proper release it was not tested and all. 
>>>>>>> It
>>>>>>> was released in order to get the git build working. If you are going to
>>>>>>> release an alpha or beta, you've got to depend on a version thats going 
>>>>>>> to
>>>>>>> be really released for use for products. carbon-identity 4.3.4 will be 
>>>>>>> the
>>>>>>> proper release to depend on. But it might take couple of weeks for us to
>>>>>>> release it completely.
>>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>> https://github.com/wso2/carbon-identity/tree/release-4.3.3/components/identity/org.wso2.carbon.identity.oauth
>>>>>>>
>>>>>>> On Tue, Apr 7, 2015 at 7:59 AM, Harshan Liyanage <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have checked for the source of org.wso2.carbon.identity.oauth v
>>>>>>>> 4.3.3 in [1] & [2]. But I could not find those components in either Git
>>>>>>>> repo or in SVN repo. But version 4.3.4 of these components are 
>>>>>>>> available in
>>>>>>>> git release 4.3.4 branch.
>>>>>>>>
>>>>>>>> We have a blocker here for CDM release due to non-availability of
>>>>>>>> OAuth2Service osgi service in org.wso2.carbon.identity.oauth v
>>>>>>>> 4.3.3 component.
>>>>>>>>
>>>>>>>> Could you please provide me the source repository link?
>>>>>>>>
>>>>>>>> [1].
>>>>>>>> https://github.com/wso2/carbon-identity/tree/release-4.3.3/components
>>>>>>>> [2].
>>>>>>>> https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/components/identity/org.wso2.carbon.identity.oauth/
>>>>>>>> [3].
>>>>>>>> https://github.com/wso2/carbon-identity/tree/release-4.3.4/components/oauth
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Lakshitha Harshan
>>>>>>>> Software Engineer
>>>>>>>> Mobile: *+94724423048*
>>>>>>>> Email: [email protected]
>>>>>>>> Blog : http://harshanliyanage.blogspot.com/
>>>>>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>>>>>>> lean.enterprise.middleware.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks & Regards,
>>>>>>>
>>>>>>> *Johann Dilantha Nallathamby*
>>>>>>> Associate Technical Lead & Product Lead of WSO2 Identity Server
>>>>>>> Integration Technologies Team
>>>>>>> WSO2, Inc.
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> Mobile - *+94777776950*
>>>>>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Prabath Abeysekara
>>>>> Technical Lead
>>>>> WSO2 Inc.
>>>>> Email: [email protected]
>>>>> Mobile: +94774171471
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> *Johann Dilantha Nallathamby*
>>>> Associate Technical Lead & Product Lead of WSO2 Identity Server
>>>> Integration Technologies Team
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile - *+94777776950*
>>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>>>
>>>
>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Technical Lead
>>> WSO2 Inc.
>>> Email: [email protected]
>>> Mobile: +94774171471
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Associate Technical Lead & Product Lead of WSO2 Identity Server
>> Integration Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+94777776950*
>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: [email protected]
> Mobile: +94774171471
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Associate Technical Lead & Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+94777776950*
Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to