Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Fri, 23 Jul 2004 1:53 AM
m1 properties to stay as is - m2 stuff has a much better alternative
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/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: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Assignee:
Reporter: Brett Porter
Created: Thu, 24 Jul 2003 1:45 AM
Updated: Fri, 23 Jul 2004 1:53 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]
