Hi Antoine,
I did some technical build changes too. defaultManifest.mf and version.txt now are
processed in the build using <expandproperties/> and not any more using tokens. The
reason for doing this is that Maven can do something similar to <expandproperties/>
but I am not sure how Maven supports @[EMAIL PROTECTED]
As I've been under the Maven cosh for ~4 weeks now, the way to do the
replace tokens is by using a <filter> in maven.
something like (look at how much redundant xml is needed for the pom...)
<build>
<filters>
<filter>file with properties in it</filter>
</filters>
<resources>
<resource>
<directory>
<filtering>true
<includes>
<include>**/file to be filtered</includes>
This is off the top of my head, and if you get it wrong, maven will
either shout from the rooftops (POM broken oh no!) or keep strangely
silent and do nothing (thus frustrating you further)
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
