Hi On Tue, Feb 7, 2012 at 6:30 AM, Afkham Azeez <az...@wso2.com> wrote:
> For this approach to properly work, we need to have proper package export > & import versions. Otherwise, say for example, two different features > require different versions of a particular bundle, then these features may > not be able to coexist. When upgrading a versions of an orbit dependency, > the should be a way to track all its dependant & change them accordingly > to avoid ending up with unnecessary jar duplication. > +1, we need to concentrate on imports and exports more than we are doing now. Its a nightmare to find issues when an orbit bundle is updated not knowingly. Regards, /Nuwan > -- > Afkham Azeez > Sent from my phone > On Feb 6, 2012 9:27 PM, "Sanjiva Weerawarana" <sanj...@wso2.com> wrote: > >> +1 for going ahead (without opinion on timing) and to Amila's suggestion >> of making the orbit stuff another TLP. >> >> I'm +1 for graphite per Senaka for X. >> >> Sanjiva. >> >> On Mon, Feb 6, 2012 at 4:03 PM, Dimuthu Leelarathne <dimut...@wso2.com>wrote: >> >>> Hi all, >>> >>> +1. >>> >>> When installing other features to different products, it should mention >>> the carbon core version. Currently, the carbon core is the intersection of >>> products, so there is no problem at all. But if we go ahead with minimizing >>> carbon-core it can be tricky to handle. Just had an offline chat with >>> Sameera, and according to him P2 handles it nicely. >>> >>> thanks, >>> dimuthu >>> >>> On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe <sume...@wso2.com>wrote: >>> >>>> +1 for the idea. B4 doing the actual change, how about running through >>>> different scenarios (like Amila mentioned) - like how we did for branching >>>> approach. Figuring out problems later would be costly in terms of time. >>>> >>>> /sumedha >>>> >>>> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma <same...@wso2.com>wrote: >>>> >>>>> *Objective*: >>>>> Make Carbon core a top level project in WSO2 trunk. At the moment >>>>> complete Carbon platform code lies under >>>>> https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its >>>>> own problems. >>>>> >>>>> *Motivations*: >>>>> 1) Carbon core can be treated as a separate product which has its own >>>>> dependencies, orbit and Carbon core can be released independently of other >>>>> Carbon components, products. >>>>> 2) To ensure that the Carbon based products can depend on a stable, >>>>> well tested and released version of Carbon instead of the Carbon trunk. >>>>> 3) This will also ensure the stability of the Carbon based products, >>>>> because they are no longer depend on the Carbon trunk which might undergo >>>>> drastic changes time to time. >>>>> >>>>> *Execution*: >>>>> Here is my proposal. >>>>> 1) We need to create two top level directories for Carbon and for >>>>> components, features and Carbon based products. Sample structure is shown >>>>> below. >>>>> >>>>> carbon >>>>> |--dependencies >>>>> |--orbits >>>>> |--core (core set of bundles.) >>>>> |--features (Carbon core features) >>>>> |--product (Carbon product) >>>>> >>>>> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva >>>>> once mentioned this name. :) ) >>>>> |--dependencies >>>>> |--orbits >>>>> |--components >>>>> |--features >>>>> |--products >>>>> >>>>> 2) In order to change the existing svn structure to a structure like >>>>> above, we need to hold all the commits, say for two to three days and >>>>> restructure the SVN, test properly and release for commits. >>>>> >>>>> Please feel free to comment. >>>>> >>>>> Thanks, >>>>> Sameera. >>>>> >>>>> -- >>>>> 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 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> /sumedha >>>> +94 773017743 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> architect...@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Technical Lead >>> >>> WSO2, Inc. (http://wso2.com) >>> email: dimut...@wso2.com >>> >>> >>> Lean . Enterprise . Middleware >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 >> 650 265 8311 >> blog: http://sanjiva.weerawarana.org/ >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > _______________________________________________ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * <http://www.nuwanbando.com/>
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
