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? --Alex > -----Original Message----- > From: Howie Yu [mailto:[email protected]] > Sent: Monday, January 07, 2013 8:59 PM > To: [email protected] > 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" <[email protected]> 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> > 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>
