On Tue, Feb 22, 2011 at 7:59 AM, Sameera Jayasoma <[email protected]> wrote:
> One more point. Say a person just need to build our ESB product. Now he > will be checking out tons and tons of code which could take hours. We need > to come up with a strategy to restructure this code base to make it less > complex and manageable for internal and external developers. > +1. What about externals set based on the products based on the product profiles, like we have recently set up Carbon for Stratos. (Carbon was set as an external for stratos - making it stratos/stratos and stratos/carbon). For eg, checking out esb will check out only the relevant carbon components, features, dependencies (which are set as externals), based on the profiles (as esb/components, esb/features, esb/product, ..). But a bit of more overhead for maintenance. Thank you. Regards, Pradeeban. > > Thanks > Sameera > > > 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. >> >> 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 >> > > > > -- > 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 > > -- Kathiravelu Pradeeban. Software Engineer. WSO2 Inc. Blog: [Llovizna] http://kkpradeeban.blogspot.com/
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
