The following comment has been added to this issue:
Author: Brian Murray
Created: Wed, 30 Jul 2003 9:16 AM
Body:
I prefer the current behavior of looking for build.properties in $HOME rather than
$MAVEN_HOME_LOCAL. Why?
1)it seems more natural to me to look for a user-specific global properties file in
$HOME. Of course, with the proposed change if you use the default value of
$MAVEN_HOME_LOCAL ($HOME/.maven) then build.properties is in $HOME indirectly.
However, we're using Windows and are overriding %MAVEN_HOME_LOCAL% so there is no
relationship between $HOME and $MAVEN_HOME_LOCAL. In this situation, it is easier to
know that you just go to $HOME to find build.properties.
2)In a multi-user environment one might want all users to share a local repository and
so instruct each user to use the same setting for $MAVEN_HOME_LOCAL. If MAVEN-605 is
implemented then these users won't be able to have personal build.properties files.
3) I like to view $MAVEN_HOME_LOCAL as a location that I can delete freely with no
risk of data loss. If build.properties were kept here, I could no longer freely
delete this location.
Sorry for the long comment. Keep up the great work.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-605
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-605
Summary: maven should load $MAVEN_HOME_LOCAL/build.properties by default
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Assignee:
Reporter: Brett Porter
Created: Thu, 24 Jul 2003 1:45 AM
Updated: Thu, 24 Jul 2003 1:45 AM
Description:
for consistency with other defaults, maven should load build.properties from
$MAVEN_HOME_LOCAL (which by default is $HOME/.maven), instead of
$HOME/build.properties.
The main issue I see with this is that maven.home.local can be specified in the
build.properties, which if you move it makes it hard to find :) Resolutions to this
are requiring they use the env. var, requiring they add -Dmaven.home.local=... to
MAVEN_OPTS, or allowing a load from $HOME/build.properties first, and then from
${maven.home.local}/build.properties.
I suggest the last as it allows the other options as well, but we should rename it to
${user.home}/maven.properties instead of build.properties
---------------------------------------------------------------------
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]
