Re: master property file
At 10:23 AM 7/24/2003 +0200, you wrote: Dominik Dahlem wrote: > 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. I am in this very situation, I've found that in some cases I can use preGoals as a hack to work round this. It's not elegant, but until property inheritance is in place it may help. For example, I added this to the master maven.xml file and it seems to work. preGoal in root maven.xml is fudging checkstyle to use geotools config settings The echo is only there to remind me to take it out once the issue is resolved. James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: master property file
Dominik Dahlem wrote: > 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. This is a known problem, everyone wants that fixed. Unfortunately it was very hard to do proprerly within the internal data model Maven was using. Right now Jason is in the middle of a major refactoring of the internals, and I hope that property inheritance will be among of the the things it will make easy/possible. R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: master property file
As I mentioned, I think this is already proposed under bugs in JIRA.
--
Brett Porter
Team Leader, Core Systems
f2 network ~ everything essential
> -Original Message-
> From: Dominik Dahlem [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 24 July 2003 6:03 PM
> To: 'Maven Users List'
> Subject: RE: master property file
>
>
> 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
>
RE: master property file
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]
Re: master property file
Great ideagotta patch?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Tomasz Pik <[EMAIL PROTECTED]> wrote on 24/07/2003 04:32:09 PM:
> 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]
>
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]
>
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]
RE: master property file
> All my subproject currently inherit the project.xml from the
> master (including goals in the master maven.xml). Wouldn't it
> be nice to be able to inherit properties on this level as well?
I think there is an issue in JIRA to make this work.
> Or is there another way of solving this problem? I don't
> wanna use a properties file in my home directory. As well,
> changing the drivers.properties appropriately has other
> disadvantes (bug MAVEN-224).
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.
You can no longer change driver.properties either - it is built into the
maven.jar and not intended to be messed with.
- Brett
master property file
Hi all, I'm looking for a solution to provide a master property file, which contains e.g. proxy and/or remote repository settings. I tried to use build.properties and project.properties in my master project. However this didn't work. All my subproject currently inherit the project.xml from the master (including goals in the master maven.xml). Wouldn't it be nice to be able to inherit properties on this level as well? Or is there another way of solving this problem? I don't wanna use a properties file in my home directory. As well, changing the drivers.properties appropriately has other disadvantes (bug MAVEN-224). Thx, Dominik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
