HI On Sat, Feb 18, 2012 at 10:19 PM, Senaka Fernando <sen...@wso2.com> wrote:
> Hi Sumedha, Pradeeban, > > Well it looks much more structured, but it does not address the concern > from Pradeeban. With this structure, someone cannot in anyway do a single > checkout of the whole thing. But in anyway, that should never be a > requirement to anyone in the future. The reason to need to checkout the > whole of carbon is totally because carbon, components and everything > related was always treated as a single chunk and this is an approach to > cleanly separate those concerns. Someone working on component Y will use or > extend the kernel, and should be able to live in total independence. But > there can be situations that a bug in the kernel limits you from doing > something. That would be similar to any other bug in Axis2. > +1, this is correct and IMO, this is what Sameera had suggested in his mail. We have three top level projects; kernal, orbit and platform, each has a separate parent pom, and each has a separate trunk and a branch, so someone who is working on a platform component can checkout the platform stuff, and work on it. he doesn't need to checkout the kernel. Same goes to the kernal. IMO, this structure is clean so +1, I also feel grouping all three of these projects as Carbon also correct coz all three of these projects are maintained as segments of WSO2 Carbon. > > From a developer's perspective, while its important that we spend time and > get things done right, I'd like to to see us agreeing on something > soon, since every move means a new checkout and a new build, which seems to > be taking an age to get through with nasty issues like the missing Jarvana > repository. > +1, true lets finalize on one thing and do a restructure, else it causes alot of valuable time. It took at least two days to get the stuff build correctly after the restructure happened last weekend. Regards, /Nuwan > > Thanks, > Senaka. > On Sat, Feb 18, 2012 at 9:18 PM, Afkham Azeez <az...@wso2.com> wrote: > >> No graphite. There never was :-) >> >> -- >> Afkham Azeez >> Sent from my phone >> On Feb 18, 2012 7:11 PM, "Sumedha Rubasinghe" <sume...@wso2.com> wrote: >> >>> +1. This looks much more structured. Also addresses the concern >>> mentioned by Pradeepan above. >>> The term graphite will no longer be used with this structure? >>> /sumedha >>> >>> >>> On Mon, Feb 13, 2012 at 5:41 PM, Sameera Jayasoma <same...@wso2.com>wrote: >>> >>>> Hi Samisa, >>>> >>>> As per the offline discussion we had with (you, Azeez, Isuru, Pradeep >>>> and others), we identified that the existing structure has its own >>>> complexities as illustrated by the Samisa. >>>> >>>> The proposal was to come up with a toplevel project called carbon and >>>> maintain the structure illustrated in the attached image. >>>> >>>> This change will be a simple SVN move. We will do this once the tomcat >>>> OSGification is applied to the carbon trunk. >>>> >>>> Thanks, >>>> Sameera. >>>> >>>> >>>> On Mon, Feb 13, 2012 at 3:59 PM, Samisa Abeysinghe <sam...@wso2.com>wrote: >>>> >>>>> Graphite brings in complexities in comprehension - is it a new >>>>> project, part of Carbon, extend Carbon etc etc >>>>> >>>>> Imagine telling a story along the lines of "Carbon has this concpet >>>>> called P2 and you install Graphite components onto Carbon products using >>>>> feature manager component" >>>>> >>>>> >>>>> On Mon, Feb 13, 2012 at 11:00 AM, Supun Malinga <sup...@wso2.com>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma >>>>>> <same...@wso2.com>wrote: >>>>>> >>>>>>> Hi Azeez, >>>>>>> >>>>>>> Let me explain the rationale behind this orbit level change. >>>>>>> >>>>>>> If you look at the orbit project keeping Carbon aside, it can be >>>>>>> considered as a third party project, completely independent from Carbon >>>>>>> and Graphite projects. The purpose of the orbit project is to produce >>>>>>> OSGi >>>>>>> bundles out of third party legacy jars. So the orbit project is not >>>>>>> related to Carbon or Graphite by any means. And also changes to these >>>>>>> orbit >>>>>>> projects is rare, unless we created them in a sloppy manner. Ideally we >>>>>>> can upload orbit projects and then developers do not need to build them >>>>>>> at >>>>>>> all. >>>>>>> >>>>>>> But, over the time we've missed used the orbit concept. e.g. we have >>>>>>> orbit projects corresponding the dependencies projects. These orbits >>>>>>> change >>>>>>> frequently, since the corresponding dependencies change. >>>>>>> >>>>>>> By considering all these aspects, we came up with the following >>>>>>> structure >>>>>>> >>>>>>> *orbit* (Consists of all the orbit projects which are used by both >>>>>>> Carbon and Graphite projects.) >>>>>>> >>>>>>> *carbon* >>>>>>> *|--* *dependencies* >>>>>>> *|-- orbit* (These orbit projects produce bundles out of the >>>>>>> Carbon level dependencies.) >>>>>>> >>>>>>> *graphite* >>>>>>> *|-- dependencies* >>>>>>> *|-- orbit* (These orbit projects produce bundles out of the >>>>>>> Graphite level dependencies.) >>>>>>> >>>>>>> Please let us know your views on this. >>>>>>> >>>>>> >>>>>> +1 >>>>>> >>>>>> thanks, >>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Sameera. >>>>>>> >>>>>>> >>>>>>> On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez <az...@wso2.com>wrote: >>>>>>> >>>>>>>> In this model,. what happens to dependencies & orbits that are >>>>>>>> common to both Carbon & Graphite? >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma <same...@wso2.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi Samisa, >>>>>>>>> >>>>>>>>> We have plans commit Pradeep's change in a hackathon mode. His >>>>>>>>> changes is again platform wide change. We can get help from the AS and >>>>>>>>> Jaggery team as well. >>>>>>>>> >>>>>>>>> Lets plan this during the todays meeting. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Sameera. >>>>>>>>> >>>>>>>>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe < >>>>>>>>> sam...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando < >>>>>>>>>> prad...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe < >>>>>>>>>>> sam...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> And do we have Tomcat OSGi stuff in there now? >>>>>>>>>>>> >>>>>>>>>>>> No, not yet. Plan is to add them within next two days. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Note that both AS and Jaggery are blocked on this. >>>>>>>>>> >>>>>>>>>> We have arrange a meeting too to discuss these today. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Samisa... >>>>>>>>>> >>>>>>>>>> Samisa Abeysinghe >>>>>>>>>> VP Engineering >>>>>>>>>> WSO2 Inc. >>>>>>>>>> http://wso2.com >>>>>>>>>> http://wso2.org >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Carbon-dev mailing list >>>>>>>>> Carbon-dev@wso2.org >>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Afkham Azeez* >>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>> * <http://www.apache.org/>** >>>>>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>>>> twitter: >>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>> * >>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>>>> >>>>>>>> * >>>>>>>> * >>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Carbon-dev mailing list >>>>>>> Carbon-dev@wso2.org >>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Supun Malinga, >>>>>> >>>>>> Software Engineer, >>>>>> >>>>>> WSO2 Inc. >>>>>> http://wso2.com >>>>>> http://wso2.org >>>>>> email - sup...@wso2.com <sup...@wso2.com> >>>>>> mobile - 071 56 91 321 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> Carbon-dev@wso2.org >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>>> Thanks, >>>>> Samisa... >>>>> >>>>> Samisa Abeysinghe >>>>> VP Engineering >>>>> WSO2 Inc. >>>>> http://wso2.com >>>>> http://wso2.org >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> /sumedha >>> +94 773017743 >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > * > Lean . Enterprise . Middleware > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *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
