I completely agree. +1 for the idea. Would it make more sense if we model your multi-module maven project as a solution project? The purpose of a solution project would be to have many different projects (logically) contained in it, that will give out artifacts as a solution for some production system when it is built.
Regards, Saminda On Fri, Mar 16, 2012 at 1:22 AM, Harshana Martin <[email protected]> wrote: > Hi All, > > From solution management perspective it completely makes sense to have a > different project other than the C-App project as the parent and it will > be the case most of the time. So i'm not sure whether we should do it or > not. > > Thanks and Regards, > Harshana > > > On Thu, Mar 15, 2012 at 10:04 PM, Harshana Martin <[email protected]>wrote: > >> Hi Saminda, >> >> On Thu, Mar 15, 2012 at 7:35 PM, Saminda Wijeratne <[email protected]>wrote: >> >>> 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? >>> >> >> No.. >> >> You are absolutely correct. We can do that. Then we can go and build that >> parent, it builds all the other modules including C-App. >> >> But there is one issue here :). >> >> When creating the project, we can point to a parent project and it has to >> be a aggregator with pom packaging. Therefore we cannot use distribution >> project as the parent project because it has the packaging type >> carbon/application to denote that it produce a car file. >> >> So we have to use some other project may be general project as the parent >> project. This is where the issue comes. >> >> If user exports from IDE, he uses C-App project to export but the maven >> user has to use some other project. So we don't have the unified experience >> when we use 2 mechanisms. >> >> If we make the above proposed change, we can get the unified experience >> where IDE user export the C-App and maven user goes and build C-App. >> >> Is there other way to fix it? >> >> Thanks and Regards, >> Harshana >> >>> >>> 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 >>>> >>>> >>> >> >> >> -- >> 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 >> >> > > > -- > 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
