> From: Dominique Devienne [mailto:[EMAIL PROTECTED] > > > Thus I come back to my question about why basedir override > was implemented in the first place. I didn't get an answer I > liked so far. Maybe it's because I always design my > build/subbuilds in such a way that any basedir override would > break them, or said differently, that the build behaves the > same way when called directly, or called from a parent/master build. >
It all goes to that ugly explanation: BC. In the beginning people had this idea of changing basedirs just to have build files that were like libraries (I never really bought into that). In the beginning there was also this idea, of "user properties" that override no matter what across everything (so I can say debug=true and it will take precedence). I never really bought onto that either because what "debug" means in buildA.xml May be different of what it means in buildB.xml. But all those polocies were decided a long time ago, and now BC is there. Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
