I thought we already solved this problem way back from the initial impl. i.e. we allow specifying the parent pom when a project is created (& that parent pom is infact the multi-module project). After that the problem sort-of solves itself when someone builds that parent pom. Am I missing something here?
Regards, Saminda On Thu, Mar 15, 2012 at 7:02 PM, Harshana Martin <[email protected]> wrote: > Hi All, > > We are planning on providing the multi module project support for Dev > Studio 2.0.0. > > In the current M9 milestone, once you create a C-App project, it gives you > the ability to include other artifacts as dependencies to your C-App. > > But currently you need to build these dependencies before hand you start > build your C-App, which is not that user friendly. > > Hence we have decided to add maven multi module project support via C-App > project. > > *Proposed Change:* > > 1. We place the pom which contains dependencies to other artifacts inside > a folder named "CApp" (we can decide about the name) - Figure1 > 2. Introduce an aggregation pom to C-App project - Figure2 > > WDYT? > > We have a public jira ticket to track the progress [1]. > > [1]. https://wso2.org/jira/browse/TOOLS-890 > > Thanks and Regards, > Harshana > -- > Harshana Martin > Software Engineer > WSO2 Inc. > Web:http://wso2.com > http://wso2.org > > Mobile: +94 716062650 > Blog: http://harshana05.blogspot.com > Profile: https://www.google.com/profiles/harshana05 > Twitter: http://twitter.com/harshana05 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
