Instead of the manifest entries (which you are filtering from your own
manifest file), you can use the <manifestFile> configuration to the
JAR plugin (or do both).
http://maven.apache.org/guides/mini/guide-manifest.html
On 15/09/06, Kevin Jackson <[EMAIL PROTECTED]> wrote:
Hi Brett,
Thanks for taking the time to trouble-shoot this - I *really*
appreciate all the help so far.
I've fixed the missing resource problem, but the Manifest file is
still not being updated in the jar file.
I have a Manifest.mf file in my src/main/resources dir, it is being
updated with the build time correctly (and put in
target/classes/META-INF. I now want this to be used in the jar
plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestEntries>
<Build-Time> -
${build.time}</Build-Time>
</manifestEntries>
</archive>
</configuration>
<executions>
<execution>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
The jar plugin is simply creating a default manifest file and ignoring
the resources file. What I really want is the src/main/resources
Manifest.mf to be appended to the end of the auto-generated
Manifest.mf
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
