Hi Ruchira, At the moment, the only way to do this is by excluding these libraries from the Jaggery distribution. Because these features comes with Carbon core. But once we do the proper minimization of Carbon core, we should be able to remove these libraries using a better way.
Thanks, Sameera. On Fri, Jun 15, 2012 at 1:55 AM, Ruchira Wageesha <[email protected]> wrote: > Hi All, > > Having feature manager components which is there by default in carbon > kernal, isn't useful for standalone Jaggery as it is not recommended to > install carbon-features in standalone Jaggery. > > The purpose of standalone Jaggery server is, offering a minimal server for > Jaggery developers. Further, we have changed axis2 repository location, > directory structure etc. in Jaggery standalone version. Hence, we need a > way to remove feature manager related components from the Jaggery build. > The only way, I can see is, excluding those jars from the Jaggery > distribution. > > Will there be any better way to handle this? > > Further, if someone wants to have both Jaggery and carbon features, then > he will need to get carbon kernal/AS and install Jaggery feature/needed > features. > > -- > *Ruchira Wageesha > Senior Software Engineer & Member, Management Committee, Development > Technologies* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com* > * > email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: +94 > 77 5493444* > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sameera Jayasoma Senior Technical Lead WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://tech.jayasoma.org Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
