Hi, On Tue, Feb 22, 2011 at 7:43 AM, Sameera Jayasoma <[email protected]> wrote:
> Hi Azeez, > > Existing Carbon code base is huge and unmanageable at the moment. If we > merge Stratos and Carbon, it would become a nightmare to maintain it. We can > restructure the Carbon code base in a manner to solve these issues. But > merging is not the solution. > > -1. > > "Carbon code base is huge and unmanageable" is a separate concern. Service version of a product is mostly the same. Technically, service = product + few more components +1 for Azeez's suggestion. Thanks, DimuthuL > Thanks > Sameera > > On Tue, Feb 22, 2011 at 7:16 AM, Afkham Azeez <[email protected]> wrote: > >> The Carbon based products & corresponding Stratos services share a lot of >> dependencies. However,these go out of sync because they are in 2 different >> locations. I propose that all Stratos service builds be moved into the >> corresponding products as Maven modules. Also, the dependencies and features >> dir could be split into carbon and Stratos & we can have the relevant >> components & features under those. This will eliminate the Stratos top level >> svn project & ensure that the product teams keep the Stratos services up to >> date. >> >> Thoughts welcome. >> >> Thanks >> Azeez >> >> ------ >> Sent from my APD® >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
