Hi, On Tue, Feb 22, 2011 at 10:01 AM, Hiranya Jayathilaka <[email protected]>wrote:
> > > 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. > > > 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? > just a few thoughts, btw, we can build the products from the products profile(eg: AppServer from products/appserver/) given that all the latest artifacts are deployed in the online maven repos. There will be complications if the user is to checkout sources only required for the products he/she needs and skipping all non related sources. In future he/she may need to use another product and will have to checkout that product specific sources to a separate location. This will be a duplication of same sources in two places and the build effort will be higher. If we want to restructure the dist. we might want to think about above scenario as well. Regards, > 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 <[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 >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
