incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <>
Subject Re: [MERGE] Merge Javelin branch into master
Date Tue, 08 Jan 2013 17:03:17 GMT
On Tue, Jan 8, 2013 at 11:58 AM, Alex Huang <> wrote:
> Hi Howie,
> Javelin has not merge into master.  This is a thread to discuss the merge process and
what the community requires before the merge happens.
> I believe you can write unit tests today.  I don't believe this is related to Spring.
 You just add <testSourceDirectory> to the pom.xml to indicate where the test directory
is.  I'm not quite sure why it deviated from the standard maven layout.  Perhaps Hugo can
shed some light on it?

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.

> --Alex
>> -----Original Message-----
>> From: Howie Yu []
>> Sent: Monday, January 07, 2013 8:59 PM
>> To:
>> Subject: Re: [MERGE] Merge Javelin branch into master
>> Hi
>> Since javelin have merge into master and start using spring framework.
>> Is possible also change project layout to formal maven layout?
>> Such as src/main/java/
>>         src/main/resources
>>         src/test/java
>>         src/test/resource
>> Someone new to this community, like me can help to write some unit test
>> for cloudstack module.
>> On 13/1/8 上午12:41, "Alex Huang" <> wrote:
>> >> IMO, the resulting merge should include fixes to any broken unit
>> >> tests.  It would be nice for there to also be unit tests for the new
>> >> classes.  Let everyone know when you are ready for help on the unit
>> >> tests fixes, and I'm sure folks will step up to help out (I'll
>> >> certainly do a few).
>> >
>> >+1 We need to fix all unit tests before merging.
>> >
>> >--Alex
>> <table class="TM_EMAIL_NOTICE"><tr><td><pre>
>> 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>

View raw message