On Tue, Feb 22, 2011 at 7:59 AM, Sameera Jayasoma <same...@wso2.com> 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. Well this happens even right now. We do checkout tons of irrelevant code to build a single product. There is no way to simply checkout the components and features required to build a particular product. It's either all or nothing. So I don't think this is a strong enough reason to not do this. Having said that I also think that this is going to complicate products builds. So I think we need to have some mechanism in place to prevent that if we are going to implement this proposal. May be some profiles defined at product level? Individuals can build either the product distro or the Stratos distro when doing a build, but the builder machine will be dealing with the default profile. Any build failures in either module should be treated as high priority and taken care of by the product teams. Thanks, Hiranya > 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. > Thanks > Sameera > > > On Tue, Feb 22, 2011 at 7:43 AM, Sameera Jayasoma <same...@wso2.com>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 <az...@wso2.com> 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 >>> Carbon-dev@wso2.org >>> 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: same...@wso2.com >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> > > > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
