nk <[EMAIL PROTECTED]>
Gesendet von: news <[EMAIL PROTECTED]>
14.07.2008 14:35
Bitte antworten an
"Maven Users List"
An
users@maven.apache.org
Kopie
Thema
Re: replace content (properties file) of deployed artifacts for custom
purposes?
Torsten;
[EMAIL PROTECTED]
pie
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 fil
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.st
Hi,
at buildtime, we deploy a generic "our-product.ear", containing a file
"version.properties".
# Datum des Builds
build.startDate=${build.startDate}
# Buildversion
productVersion=${productVersion}
# Productname
productName=${productName}
At delivery time we need to "patch" the version.pro
