-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Hi,
Hi there,
as often I a little late on some threads ;)
> I have start a proposal [1]
so far so good.
I have the following suggestions:
1. Also specify that the pom.filters are in the order of their declaration in
the XML.
2. Resolve variables whenever they are requested.
What I mean is that I can do
filter1.properties:
var1=Foo
var3=${var2}/Thing
filter2.properties:
var2=${var1}-Bar
So if I resolve ${var3} I get "Foo-Bar/Thing".
That would be an excellent feature, since I am using
maven for deploying a large system and therefore
build it as multiple debian-packages with
seperation of application- and configuration-packages.
The configuration packages are build for
production as well as for 14 different
testing-environments. Various ports, hostnames, etc.
slightly differ in these environments. I could avoid
a lot of redundancies and daramtically simplify my
filters with the features described above.
Do I need to file a JIRA ticket or is this enough
input?
My suggestion to implement this, would be to
create chains of "Properties" that inherit
from their parent and resolve this in
"getProperty()". However you might not want to
use your own API defined as clean interface
instead of Properties.
Thanks
Jörg
>
> Thanks for comments,
> --
> Olivier
>
> [1]
> http://docs.codehaus.org/display/MAVEN/Resources+Handling+(common+component+maven-filtering)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI2pjzmPuec2Dcv/8RAj+JAJ9CuWvkh8A+UbHxgJfksaIPQbT5hQCfete7
XejVhEEoWmQxfpIvgoLLJJ4=
=xaPy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
