Message: The following issue has been closed.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVEN-841 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-841 Summary: allow maven to treat a file in ${user.home} as a source of default properties Type: New Feature Status: Closed Priority: Major Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0-rc3 Assignee: Reporter: Colin Sampaleanu Created: Mon, 22 Sep 2003 10:41 AM Updated: Fri, 23 Jul 2004 1:55 AM Description: As per recent mailing list discussion, Maven currently treats ${user.home}/build.properties (aka ~/build.properties on unix systems) as an optional source of properties which override similarily named properties read from any project.properties or build.properties in the project dir. While this is a valid need, there is at least as much of a need to have Maven read another optional file (name to be determined) in ${user.home) as a source of _default_ properties, where any properties read from this file are overriden by values in project.properties and build.properties in the project dir. The actual name of this file is not as important as the need for this capability. To maintain strict backwards compatibility with existing Maven beta versions, ~/build.properties processing could remain unchanged, and the new defaults file would be called something like ~/maven.default.properties. In my opinion, I do think that it makes more sense to rename the existing file to something like ~/maven.override.properties, and have the defaults file be called ~/build.properties. This is because - more than half the ant projects I found seem to do that, as opposed to the other way around. It is important to make the transition from ant to maven easy. - when Maven starts supporting extending project.properties and build.properties from a root project to a subproject, similar in fashion to how project.xml is currently extended, the lower level definition will win out. On this basis, ~/build.properties is the definition the farthest away from the project dir itself, so it should have the least important. - I do not believe renaming the existing global override file will affect many users, since the globabl override feature is so powerful (it affects all maven projects including future ones that you may bring in, with no way to not have the override) that most people would not be using it at all or have very many entries in there. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
