Hello,
I am still stuck with a mechanism, that I used a lot when writing
build and deploy systems for many developers and configurations with
ant. The main goal here is to avoid redundancy when listing
configuration properties, using a default build.properties and then
selectively override special property setting for a developers
enviromnent or for the target systems. Example:
build.xml:
<propertyfile name="${user.name}.properties"/>
<propertyfile name="${hostname}.properties"/>
<propertyfile name="build.properties"/>
buid.properties:
prop1=val1
prop2=val2
prop3=val3
prop4=val4
prop5=val5
hostname.properties:
prop2=otherval
user.properties:
prop5=otherval
That way I never have to touch all existing properties, if I add a
new config value, i.e. to build.properties.
If I use profiles to modify the build element of the POM, I have to
inject a quite complete copy of the original build element. And, if I
try to list multiple filters int the filters element, the behaviour
is also not very obvious. Seems that only one of the
filter.properties files is in effect.
Is there a way to adjust properties non-redundant when using
profiles, or did I miss a maven feature, that does exactly that?
Thank you for reading
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
