On Sun, Mar 4, 2012 at 7:49 PM, Pradeep Fernando <[email protected]> wrote:
> Hi, > > IMHO , we should make product builds independent from each other. That is, > a product should be able to build on its own, (NO pom inheritance) . We can > introduce a aggregate pom, to maintain the same user experience. (you build > from product level, you get all the products.) > > +1 Idea is products should be self contained. And when we update the artifacts snapshot repo even people should be able to create there own product too by adding removing features. They should be able to look at the existing product pom structure (one which is suggested here) and create there own products. (Ideally we provide a mvn archetype). thanks, Charith > With the above kind of structure, you can see the exact products that are > failing. its the product teams responsibility to go and fix the respective > product. In addition, it allow us to introduce a new product without > worrying about build breaks. (for an example, the jaggery is not in the > build system). > > we (charith, sameera and shammi) had informal discussions on the above > $subject sometime back. > > For the time being, i'm +1 for your suggestion. In fact i have excluded GS > and MS. The idea was to get a build-success mail. But product p2-profile > gens failing due to registry core feature. > > Thanks, > --Pradeep > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Charith Dhanushka Wickramarachchi Software Engineer WSO2 Inc http://wso2.com/ http://wso2.org/ blog http://charithwiki.blogspot.com/ twitter http://twitter.com/charithwiki Mobile : 0776706568
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
