The following comment has been added to this issue:

     Author: Martin Skopp
    Created: Tue, 21 Oct 2003 3:41 AM
       Body:
So I identified 2 options for the directory:
(1) $HOME
(2) $MAVEN_HOME_LOCAL (=$HOME/.maven per default)

and 3 options for the filename:
(a) build.properties
(b) .mavenrc
(c) maven.properties

Where the combination (1a) is the beta-10 behaviour and a pain.
Changing the filename is IMHO not _required_ if the directory is changed to (2) [but 
possibly nice-to-have-anyway].

Argument (i):
For filename, I prefer (a)+(c) over (b) 'cause a extension .properties indicates it's 
a properties file which it is.  I also prefer (c) over (a) since it puts emphasis on 
being a _maven_ properties file.

Argument (ii):
In general, I prefer a (Unix) hidden file, so I like hidden directory (2) most. (b) 
could be a alternative but does not have .properties extension, see (i).

For a voting, here are my favourites:
=====================================
So my Voting goes to (2) in general, (2c) if the filename is taken into account.  If 
we stick to (1), I would choose (b) since it's hidden.
---------------------------------------------------------------------
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
   Fix Fors:
             1.1

   Assignee: 
   Reporter: Brett Porter

    Created: Thu, 24 Jul 2003 1:45 AM
    Updated: Mon, 4 Aug 2003 10:35 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]

Reply via email to