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. Thanks, Sameera. On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez <[email protected]> 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 <[email protected]>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 <[email protected]>wrote: >> >>> >>> >>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe <[email protected]>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 >>> [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 >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> 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: **[email protected]* <[email protected]>* 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 > [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
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
