Hey, While I'm more than happy to migrate the sources to the maven "standard" layout, we didn't do this yet. The reasoning was that we were running in a hybrid situation with both maven and ant for a while. 4.1 will be the first release with a "full" maven build.
My proposal would be to leave this till 4.1 is out the door. My current focus is getting packaging done and remove waf. Once that is finished we can focus on cleaning up the sources and making everything look more like a maven structure. As far as I know this is purely cosmetic, so we have no pressing reason to do it right now. Cheers, Hugo -----Original Message----- From: Howie Yu [mailto:howie...@trend.com.tw] Sent: woensdag 9 januari 2013 2:58 To: cloudstack-dev@incubator.apache.org Subject: Re: [MERGE] Merge Javelin branch into master Hi Alex Yes, You are right . I can add testSourceDirectory into pom.xml. I just want to make sure why not use maven conversion layout ~:) If I write any unit test for any module , should I still follow the standard way post my code into review board? Beside, I find Javelin branch have some error on pom.xml file , can I report here? -------------------------- incubator-cloudstack/framework/ipc/pom.xml) has 1 error Not authorized, ReasonPhrase:Unauthorized. and 'parent.relativePath' points at wrong local POM @ line 15, column 11 -> I think the pom.xml of cloud-framework-ipc use wrong parent The parent pom should be cloudstack-framework <parent> <groupId>org.apache.cloudstack</groupId> <artifactId>cloudstack-framework</artifactId> <version>4.1.0-SNAPSHOT</version> <relativePath>../pom.xml</relativePath> </parent> Not cloud-engine <parent> <groupId>org.apache.cloudstack</groupId> <artifactId>cloud-engine</artifactId> <version>4.1.0-SNAPSHOT</version> <relativePath>../../pom.xml</relativePath> </parent> On 13/1/9 上午1:08, "Alex Huang" <alex.hu...@citrix.com> wrote: >> The problem that Howie is talking about is that none of our projects >> are structured in the "standard" maven layout. This isn't just a >> test source issue. >> >I'm saying maven have a way to accommodate for that by specifying >exactly where the directory should be in the pom.xml. > >Like I said though, I don't know why it doesn't follow standard layout. >Maybe it was just easier to do the maven conversion this way? I think >all the directories in javelin has follow the current layout in 4.0 as >well. We can make all of the javelin directories follow the standard >if there was no clear call on how to layout the structures originally. > >--Alex <table class="TM_EMAIL_NOTICE"><tr><td><pre> TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. </pre></td></tr></table>
