> -----Original Message-----
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September 21, 2003 3:43 PM
> To: Maven Developers List
> Subject: Re: Why is build.properties from ${user.home} the most dominant
>
>
> [EMAIL PROTECTED] wrote:
>
> > The idea is that the user knows what he wants, not the project builder.
>
> I thought that the difference between project.properties and
> build.properties was the the former were created by the project's
> vendor and the latter by the person who is building the project
> and are supposed to contain machine-specific settings that should
> not be shared through an SCM system.
> Because of that it makes sense to have both project.proerties and
> build.properties in a single project directory at the same time.
> Additionally Maven allows the user to set properties in
> ~/build.properties file. Currently the settings from this file
> override the settings from project's build.properties file.
> Both of the files say what the user (project builder) wants, not the
> project vendor, it's just the matter of specificality (<- correct
> english???). The settings in project's build.propertis say what
> the user want for this particular project and thus should override
> what the user wants generally. That's why I think Colin's request
> is valid.
>
> R.
I also see this as Rafal does.
We didn't have any compliments because current processing order is forcing
users
to use ${user.home}/properties for what they are meant for: for keeping
common settings
which are shared between all project.
At the moment what you put to this file is affecting 100% of the projects.
If this is our choice - "all or nothing" - I am OK with that.
But this sometimes can be a problem.
I have once worked on project which has a content of maven.local.repo kept
in CVS and
IMHO it was wise decision in this particular case (very tight security
policy).
With the current processing order I was unable to override this property for
this particular project.
(which would be very helpful)
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
