Hi Nuwan, That's what's desired, but it is not what you find in practice, :). Take a look @ platform/dependencies and then platform/dependencies/orbit. So, you find things that are not inside platform/dependencies to be referenced inside platform/dependencies/orbit. Such things are directly taken from outside too.
Thanks, Senaka. On Wed, May 22, 2013 at 10:14 AM, Nuwan Bandara <nu...@wso2.com> wrote: > Hi, > > Well, platform/orbit and kernal/orbit has its meaning right. if we put > some non osgi components to kernal/dependencies we wrap it at kernal/orbit. > but top level orbit is the stuff we directly take from outside. So IMO > there is a meaning in having top level /orbit. its not confusing, its > rather clean. but ofcause you can have kernal/orbit with everything needed > for kernel. > > Regards, > /Nuwan > > > On Wed, May 22, 2013 at 9:45 AM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi Miyuru, >> >> IMHO, I see no point in having a separate orbit, so I too am +1 for this. >> A separate orbit has always been a confusion, since you also find orbit >> inside kernel/dependencies and platform/dependencies, making it highly >> confusing for anyone who tries to understand (or explain) our SVN structure. >> >> Thanks, >> Senaka. >> >> >> On Wed, May 22, 2013 at 9:24 AM, Miyuru Wanninayaka <miy...@wso2.com>wrote: >> >>> Hi all, >>> >>> What is the point of having a separate orbit? [1] >>> >>> We either release kernel or platform and we don't release orbit. So any >>> orbit bundle which required for kernel can live inside >>> kernel/dependencies/orbit and platform required orbits can live inside >>> /platform/dependencies/orbit >>> >>> [1] https://svn.wso2.org/repos/wso2/carbon/orbit/ >>> >>> -- >>> Miyuru Wanninayaka >>> Technical Lead >>> Member, Management Committee - Integration Technologies >>> WSO2 Inc. : http://wso2.com >>> >>> Mobile : +94 77 209 9788 >>> Blog : http://miyurudw.blogspot.com >>> Flickr : http://www.flickr.com/photos/miyuru_daminda >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> 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 >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Thanks & Regards, > > Nuwan Bandara > Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > -- *Senaka Fernando* Member - Integration Technologies Management Committee; 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
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
