Hi,
I know about filtering - but that´s not what I want exactly.
My problem is that we build (and deploy) the ear at one time (filtering is
done at build time), but the delivery of the ear into our product (ears,
wars, documentation and so on) is separated.
I need to patch the ear at delivery time to introduce some customer
specific properties.
This is because we ship exactly the same ear to different customers -
differing only in one properties file, located in the ear.
One solution could be to build the ear only at delivery time, where the
customer is known - but that´s not what i want, because we also need the
ear at developement time,
where the customer is unknown...
Thanx, Torsten
Kristian Rink <[EMAIL PROTECTED]>
Gesendet von: news <[EMAIL PROTECTED]>
14.07.2008 14:35
Bitte antworten an
"Maven Users List" <users@maven.apache.org>
An
users@maven.apache.org
Kopie
Thema
Re: replace content (properties file) of deployed artifacts for custom
purposes?
Torsten;
[EMAIL PROTECTED] schrieb:
> # Datum des Builds
> build.startDate=${build.startDate}
>
> # Buildversion
> productVersion=${productVersion}
I believe that maven resource filtering does pretty much what you want,
only I am not sure how / whether or not to determine things like
"build.startDate" to be automatically included in there:
http://maven.apache.org/guides/getting-started/index.html#How_do_I_filter_resource_files
Cheers,
Kristian
--
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771 "One
dreaming alone, it will be only a dream; many dreaming together is the
beginning of a new reality." (Hundertwasser)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
