On Tue, Feb 22, 2011 at 11:04 AM, Isuru Suriarachchi <[email protected]> wrote:
> If I wasn't clear enough, I'm in agreement with this idea. I also think >> this will reduce the number of points to update when we are making platform >> wide changes. But we need some way to selectively build the product or the >> cloud version of the product. >> > > +1. I also think that Azeez's suggestion can be easily implemented using > separate maven profiles. Having modules like p2-profile-stratos and > distribution-stratos won't create any problems. Those will be built only > when the cloud profile of the product is built. > > And also AFAIK, there are very few stratos related components and features > which takes very little time to get built compared to our platform. So those > won't make much difference to the build. Only think is we have to manage > maven profiles correctly to resolve complications. > I'm +1 for the proposal but not for having profiles. That means people won't build the other part :). As you noted Isuru the number of components in Stratos is very small and hence the extra build time should be very little. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
