Thanks for the reply, Mike. The properites are defined in the parent
pom.xml (in order that they're inherited by the various sub-
projects). Putting them in an external file is no use to me here.
Anyway, it appears that a correctly filtered target/classes/META-INF/
MANIFEST.MF *IS* created. It just isn't being copied to the jarfile.
If I rename this to something NOT in META-INF/, it DOES get copied to
the jarfile.
So it looks as though you're meant to use the maven-jar-plugin in
order to copy stuff into the jarfile's META-INF directory. The
question is, does it support filtering?
On 31 Mar 2006, at 23:49, Mike Perham wrote:
If you are trying to filter custom properties, you need to add a
filters.properties which explicitly enumerates your filter variables.
See the Getting Started guide to filtering. It is wrong when it says
you can just filter straight from a system property into your
src/main/resources/application.properties file.
-----Original Message-----
From: Rob Dickens [mailto:[EMAIL PROTECTED]
Sent: Friday, March 31, 2006 4:25 PM
To: Maven Users List
Subject: filtering of MANIFEST.MF?
Dear Maven Users,
I've so far discovered how to merge in my own manifest file entries:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</
manifestFile>
My question now is, how can I filter this? (substitute the value of
each
${property})
I tried adding the following, but it doesn't appear to work:
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
Any ideas?
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
