system scope implies that the dependency is already on the system
classpath, so maven does not need to add it
Sent from my iPod
On 24 Nov 2008, at 04:34, youhaodeyi <[EMAIL PROTECTED]> wrote:
I use maven-jar-plugin to handle the manifest file, see below
configuration:
<manifest>
<addClasspath>true</addClasspath>
...
And I have a dependency with system scope:
<dependency>
<groupId>protocol</groupId>
<artifactId>protocol</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${basedir}/src/main/libs/protocol.jar</
systemPath>
</dependency>
But when run the command "mvn package" and the manifest file in the
jar
doesn't contain this dependency.
How can I fix this?
thanks.
--
View this message in context:
http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
