RE: [Springframework-developer] Mock Objects

[Trevor C. <pr...@se...>]

We do the same thing with plain ant and "default.properties".

T

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Colin Sampaleanu
Sent: September 20, 2003 3:25 PM
To: Rod Johnson
Cc: spr...@li...
Subject: Re: [Springframework-developer] Mock Objects


btw, I don't know if it's worth making a change, but more often than 
not, the general practice with ant projects and maven projects that I've 
seen is to have build.properties be a file which is not checked into CVS 
(sometimes there is a build.properties.sample checked in), with this 
file used for developer specific overrides. Maven adds an optional 
project.properties file, which generally _is_ checked in if it exists. 
Properties from project.properties are overriden by properties from 
build.properties.

I'm a big fan of consistency where it doesn't hurt anything, so maybe it 
makes sense to rename build.properties to project.properties, and have 
something like this at the top of the build.xml file

  <!-- Load local and user build preferences -->
  <property file="${user.home}/build.properties"/>
  <property file="build.properties"/>
  <property file="project.properties"/>

This is consistent with Maven's order, although personally I've always 
thought that making the build.properties in the user home the most 
dominant was somewhat backwards; I think it should be the source of 
defaults, but be overriden by project properties.

Regards,
Colin

Rod Johnson wrote:

>Thanks Colin, I've fixed this.
>
>----- Original Message ----- 
>From: "Colin Sampaleanu" <col...@ex...>
>To: "Rod Johnson" <rod...@in...>
>Cc: <spr...@li...>
>Sent: Friday, September 19, 2003 11:42 PM
>Subject: Re: [Springframework-developer] Mock Objects
>
>
>  
>
>>Test running seems to be broken, with the build.properties and build.xml
>>that's in CVS. That is,
>>
>>            <batchtest fork="yes" todir="${reports.dir}">
>>                <fileset dir="test" includes="${test.includes}"
>>excludes="${test.excludes}"/>
>>            </batchtest>
>>
>>should be
>>
>>            <batchtest fork="yes" todir="${reports.dir}">
>>                <fileset dir="${testbuild.dir}"
>>includes="${test.includes}" excludes="${test.excludes}"/>
>>            </batchtest>
>>
>>or no tests run...
>>
>>
>>Rod Johnson wrote:
>>
>>    
>>
>>>I've now updated all the deprecated EasyMock APIs in the test suite.
>>>      
>>>
>Please
>  
>
>>>remember to update before working on any tests: I've modified a large
>>>proportion of the test suite.
>>>
>>>Regards,
>>>Rod
>>>      
>>>





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 19/08/2003