> > But that doesn't solve problems of Windows vs. Unix builds, because > > directory paths are significantly different. Environment variables > > ensure path references are homogeneous across platforms, whereas a > > build.properties file that specify paths is system > dependent thing and > > is generally a bad idea.... > > eh - say what ? > > Ant handle all that! > If you just make a build.properties and uses thoese from within ant - > then you have platform independence out of the box! No > problem with it! >
That being said (as my initial rationale), I see a smart checking system for properties files (as you said). First I will load a default.build.properties file, then a ${basedir}/build.properties file (if it exists, to override any values that were in the default file), and finally a ${user.home}/hibernate.build.properties (if it exists, to override any values read in so far).
Please! Use standard ant "semantics" - first time you set a property you cannot change it again. Thus your loading sequence must be reversed!
First ${user.home} then etc.
;)
/max
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
