On Thu, Feb 13, 2014 at 5:05 PM, Thilini Ishaka <[email protected]> wrote:
> Yes, we are planning that for the next release which is due in May. > Then for the time being can you depended on already released version ? if it's possible we don't need to bring this component into GitHub. Thanks ! > > Thanks > Thilini > > > > On Thu, Feb 13, 2014 at 4:46 PM, Anjana Fernando <[email protected]> wrote: > >> Hi, >> >> OK, but we would need to do it soon, by figuring out what the issues are, >> it doesn't make sense to have two of these components to be in the same >> server. >> >> Cheers, >> Anjana. >> >> >> On Thu, Feb 13, 2014 at 4:13 PM, Thilini Ishaka <[email protected]> wrote: >> >>> Hi Anjana, >>> >>> BPS still depends on the old datasource component. Due to few issues we >>> encountered, we are unable to migrate to new datasource component. This has >>> already been communicated in different mail threads. >>> >>> Until we move to ndatasource component, we need to keep the old >>> datasource component. >>> >>> Thanks >>> Thilini >>> >>> >>> On Thu, Feb 13, 2014 at 3:44 PM, Anjana Fernando <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> Actually no one should be actually using the old data source component, >>>> we should move everything to the new data sources component. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>> On Thu, Feb 13, 2014 at 3:05 PM, Thilini Ishaka <[email protected]>wrote: >>>> >>>>> ESB team, do you need old datasource component? As I see there's a >>>>> dependency for that. please confirm. >>>>> >>>>> Thanks >>>>> Thilini >>>>> >>>>> >>>>> >>>>> On Thu, Feb 13, 2014 at 2:52 PM, Thilini Ishaka <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> BPS depends on *unified-endpoint* and *old datasource* features. >>>>>> Are there any product teams who use these? >>>>>> >>>>>> If no other product team needs above two features, we can maintain >>>>>> those under *'carbon-business-process*' or '*bps*' project category >>>>>> according to the new structuring. >>>>>> I think 'carbon-business-process' is more appropriate rather than >>>>>> keeping it under product. >>>>>> >>>>>> Also we have another option to depend on the release version of above >>>>>> features without moving the code to github at this point since we do not >>>>>> have major requirements to change the existing code of these 2 features. >>>>>> >>>>>> Thoughts welcome! >>>>>> >>>>>> Thanks >>>>>> Thilini >>>>>> >>>>>> -- >>>>>> Thilini Ishaka >>>>>> Senior Software Engineer >>>>>> Phone: +94 11 214 5345 >>>>>> WSO2 Inc. http://wso2.com >>>>>> >>>>>> blog: thiliniishaka.blogspot.com >>>>>> linkedin: http://lk.linkedin.com/in/thiliniishaka >>>>>> twitter: https://twitter.com/#!/ThiliniIsh >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thilini Ishaka >>>>> Senior Software Engineer >>>>> Phone: +94 11 214 5345 >>>>> WSO2 Inc. http://wso2.com >>>>> >>>>> blog: thiliniishaka.blogspot.com >>>>> linkedin: http://lk.linkedin.com/in/thiliniishaka >>>>> twitter: https://twitter.com/#!/ThiliniIsh >>>>> >>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Technical Lead >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> Thilini Ishaka >>> Senior Software Engineer >>> Phone: +94 11 214 5345 >>> WSO2 Inc. http://wso2.com >>> >>> blog: thiliniishaka.blogspot.com >>> linkedin: http://lk.linkedin.com/in/thiliniishaka >>> twitter: https://twitter.com/#!/ThiliniIsh >>> >> >> >> >> -- >> *Anjana Fernando* >> Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > Thilini Ishaka > Senior Software Engineer > Phone: +94 11 214 5345 > WSO2 Inc. http://wso2.com > > blog: thiliniishaka.blogspot.com > linkedin: http://lk.linkedin.com/in/thiliniishaka > twitter: https://twitter.com/#!/ThiliniIsh > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
