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.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
