There is even second use case besides the releaseDate that the filtering
can't cut:
Depending on a variable, for example
release.database = mysql
Certain hibernate properties should be set, such as the hibernate
dialect and the jdbc url, depending on a condition based on the
release.database value.
With kind regards,
Geoffrey
Vincent Massol wrote:
-----Original Message-----
From: David Jackman [mailto:[EMAIL PROTECTED]
Sent: mercredi 19 octobre 2005 18:37
To: Maven Users List
Subject: RE: [m2 & m1]Inject POM values into application
In m2, you just turn filtering on for resources in your pom. Assuming
you've put the files being filtered in the default place
(src/main/resources), you may not have anything about resources in your
pom already, so you'll need to add everything about this resource
directory:
<project>
...
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
</project>
With that, any resource file that contains ${pom.version} will replace
that text with the value from the version element of the pom. The same
is true for other values in the pom. I don't think values from
settings.xml are available, however. Someone else can correct me if I'm
wrong.
Agreed, this would solve one use case.
However imagine the case where you have a SNAPSHOT version. When you release
something you want that version to be resolved to a timestamp. Thus if
you're putting this version on say a web page (hint: continuum's web page)
you'd like to see the resolved timestamp value and not the SNAPSHOT.
Any idea how to do this?
Thanks
-Vincent
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
