Ok, I only put the properties needed directly by the pom into a
settings.xml profile and kept everything else in a properties file used for
filtering. That's not so bad.
On Mon, Jan 30, 2012 at 6:58 PM, Shane StClair wrote:
> Ugh...really not a fan of keeping project specific configuration
> prop
Ugh...really not a fan of keeping project specific configuration properties
in a global file like settings.xml (and of course not in the project pom).
That's really the Maven way, eh?
On Mon, Jan 30, 2012 at 4:51 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 30 January 2012
On 30 January 2012 20:09, Shane StClair wrote:
> Hello all,
>
> I have a project with a parent pom and child modules. Configuration
> properties are kept in a build.properties file and an overriding
> custom.build.properties. The properties-maven-plugin is defined in the
You are off the reservati
Hello all,
I have a project with a parent pom and child modules. Configuration
properties are kept in a build.properties file and an overriding
custom.build.properties. The properties-maven-plugin is defined in the
parent pom to load these properties, and the plugin is inherited by the
child poms.
