In my opinion, a build.properties file with user settings
should be in ${user.home}/.maven/ as Brett pointed out.
However, on another level I'd like to share project-specific
settings as well in a similar fashion to the extension mechanism
of the project.xml file. The settings which are project- rather than
user-specific include repository, xdoc, and
checkstyle settings.
This master project property file can be kept in source
control and provides a single location for settings shared
among sub-projects. Imagine you have 50 sub-projects and each
of them contains a project properties file with settings
which could well be shared. It's maintenance hell, if properties
are likely to change.
Cheers,
Dominik
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 24 July 2003 07:44
To: 'Maven Users List'
Subject: RE: master property file
Good point. I've raised MAVEN-605.
Please take a look and let me know your thoughts.
Cheers,
Brett
--
Brett Porter
Team Leader, Core Systems
f2 network ~ everything essential
> -----Original Message-----
> From: Tomasz Pik [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 24 July 2003 4:32 PM
> To: Maven Users List
> Subject: Re: master property file
>
>
> Brett Porter wrote:
> >
> > Is there a reason for not using
> ${user.home}/build.properties? In my
> > experience, this is the best solution as it usualy has user
> specific
> > options, but they are shared across all projects.
>
> Maybe it will be better to load this file from
> ${user.home}/.maven/build.properties?
> Since b10 every Maven user has such directory so why
> don't put this file there?
>
> Tomek
>
> > - Brett
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
