systemPath :
is used only if the the dependency scope is system . Otherwise, the build will
fail if this element is set. The path must be absolute, so it is recommended to
use a property to specify the machine-specific path (more on properties below),
such as ${java.home}/lib . Since it is assumed that system scope dependencies
are installed a priori , Maven will not check the repositories for the project,
but instead checks to ensure that the file exists. If not, Maven will fail the
build and suggest that you download and install it manually.
(http://maven.apache.org/pom.html)
-----Message d'origine-----
De : youhaodeyi [mailto:[EMAIL PROTECTED]
Envoyé : mardi 3 juin 2008 10:36
À : users@maven.apache.org
Objet : How can I use relative path for System Dependencies
I use system dependency. But it doesn't work when specify a relative directory
for systemPath, see below.
<dependencies>
<dependency>
<groupId>test</groupId>
<artifactId>test</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>dependency/my.jar</systemPath>
</dependency>
</dependencies>
--
View this message in context:
http://www.nabble.com/How-can-I-use-relative-path-for-System-Dependencies-tp17618779p17618779.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]
