Hal Arnold wrote:
Okay, I read that, but is there a way to either use non-standard
*.properties files or *.properties in a non-maven approved directory? Or
is that dysfunctional, and I shouldn't be doing it?
Sure, you can load property files with the
Wether it is dysfunctional or not is a subje
2005 12:23 PM
To: Maven Users List
Subject: Re: how to 'point' to another properties file
Remember the Maven hierarchy is
/project.properties
/build.properties
/build.properties
command-line
With the last one being the value taken. Which is why I put the defaults
in /project.properties
Remember the Maven hierarchy is
/project.properties
/build.properties
/build.properties
command-line
With the last one being the value taken. Which is why I put the defaults
in /project.properties. The developer can then either put
project specific values in /build.properties or Maven global
val
Eric,
Thanks for your suggestions. each developer is working more than 5
projects as same time. All the build script have to be in CVS. This may
not work well. However, do you know if this will work:
1 Check in a build-dev.property.
2 When called maven, if /build.property does not exist, copy
fr
David Cao wrote:
Thanks for the help. I had studied all these option very carefully
before. But they won't work for us.
All our sources are in source control system. The requirement is that
anybody can reproduce the build without knowing the application by
retrieving the sources. project.property
> Hope this helps.
>
> ..Russ Jubenville
>
> -Original Message-
> From: David Cao [mailto:[EMAIL PROTECTED]
> Sent: February 23, 2005 13:35
> To: Maven Users List
> Subject: Re: how to 'point' to another properties file
>
>
> Hi, this is a
helps.
..Russ Jubenville
-Original Message-
From: David Cao [mailto:[EMAIL PROTECTED]
Sent: February 23, 2005 13:35
To: Maven Users List
Subject: Re: how to 'point' to another properties file
Hi, this is a real need. I need:
1 Change the property file name by command line;
2
Hi, this is a real need. I need:
1 Change the property file name by command line;
2 Or, change the property value in Maven.xml (the current solution only
enable change to properties to plugin, which is not good enough in my
case).
I had been working on creating a process to use Maven in our produ
Sorry if this has been asked and answered, but I searched to no avail:
I'm autogenerating hibernate mappings and so I have my usual
project.properties file with the following:
maven.xdoclet.hibernatedoclet.fileset.0=true
maven.xdoclet.hibernatedoclet.fileset.0.dir=${maven.src.dir}/java
ma
