But as you can see, product teams are not taking the responsibility of maintaining the profiles of the respective Stratos Services. Unless someone in the Stratos team looks at the product, the product team is not even aware whether their Service starts up. Also, you can see that there are inconsistencies in the bundles between the Product & Service. So, even if we have two P2 profiles, it will not solve the problem of product teams testing their Services. To be fair to the product teams, it is not easy to test the Stratos Services because you need to setup MySQL, IS, Manager etc. before you can run your Service. We need to address that problem. For example, Stratos AS should be just as easy to startup as the Carbon AS.
On Fri, Mar 23, 2012 at 1:41 PM, Pradeep Fernando <[email protected]> wrote: > Hi all, > > we discussed this sometime back. The proper way to do this would be to use > p2-profiles. For an example, Our product distribution will have two > p2-profiles. One for standalnoe product and, one for service. > > The product profile will have the bundles that are only needed for > standalone product functionality. Both product and service profiles will > share the same set of bundle repository (/plugins). > > We assigned chethiya for this work. > > --Pradeep > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/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*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
