the POM (both in XML and properties form) are already included in the
JAR by default, so you can retrieve the version from those.
Also see: http://maven.apache.org/guides/mini/guide-manifest.html for
how to add the version to the manifest itself.
- Brett
On 11/12/2008, at 4:10 AM, John Coleman wrote:
I didn't want a classpath entry, so I decided to include the pom in
the
JAR as a workaround.
Thanks,
John
-----Original Message-----
From: Richard Chamberlain [mailto:[EMAIL PROTECTED]
Sent: 10 December 2008 13:36
To: Maven Users List
Subject: RE: Dependency version in manifest
You can specify the dependencies on the classpath of a manifest:
<plugins>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
</configuration>
</plugin>
<plugin>
See the Jar Plugin documentation:
http://maven.apache.org/plugins/maven-jar-plugin/
Is that what you were after?
Regards,
Richard
-----Original Message-----
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: 10 December 2008 11:21
To: Maven Users List
Subject: Dependency version in manifest
Is there a way to inject the dependency version info of a
project into the JARs manifest?
TIA
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
