> I'm going to keep sending this till we get an answer! Alternatively you > can have a complete Maven novice like me start fooling around and moving > stuff in SVN if you prefer :)
According to the maven2 build structure it is easy having what we have now , but I know we can merge webapps module and core module, and then write code in pom.xml to create separate artifact. I personally like to keep the pom.xml cleaner , if you look at our pom.xml they are much cleaner and we only use maven2 pugings to do the work. So we do not need to do much or work once we have the directory structure set up. Let's take a vote and see how many of like the current sructure, if some one is +1 on that he has to tell why he like the structure , same way if some one -1 on that then he has to say why he does not like that. :) Apache way :) -Deepal > > Paul > > Paul Fremantle wrote: >> A long while back we discussed whether there was really a need for a set >> of Maven modules. I thought - maybe incorrectly - that we had come to a >> consensus that there was no need. >> >> If that is the case, then I would like us to refactor the maven build >> asap. >> >> Ideally, we can have a single tree which builds the standalone library >> and WAR by default, with specific targets if you just want one or >> t'other. >> >> Paul >> > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > Office: +1 646 290 8050 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > _______________________________________________ > Registry-dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/registry-dev > _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
