I think it is the bug which is fixed in maven 1.0.2. Check the archive rightafter 1.0.1 came out.
-D On Wed, 12 Jan 2005 15:44:29 -0300, Tedi Itamar Zanfolim <[EMAIL PROTECTED]> wrote: > Hi, > > When I put a build.properties file in the user local home directory I can > see that my project properties are correctly overriden and maven uses these > values itself for, for example, the remote repository from where to download > artifacts. I�ve been trying to move this build.properties file to the same > directory as the parent (master) project definition, but these properties > does not seem to be overriden (if I echo the property it seems to be, but > maven itself seems to be ignoring them). The properties I want to override > are the behavioural ones, such as 'maven.repo.remote'. > > Is that supposed to work or should I keep the more generic build.properties > file in each developer home directory? > > TIA, > > Tedi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
