Personally I don't use it, but I've seen it being used in Tobago...
You could use this if your software has a dependency to e.g. 'tools.jar' from
the JDK. This dependency CAN NOT be downloaded
from the repository and therefor can be set either to 'provided' or 'system'.
If you set it to system, you can let maven check for
its existence, whereas provided can't do such a thing.
Snippet from Tobago:
<dependency>
<groupId>sun.jdk</groupId>
<artifactId>tools</artifactId>
<version>1.5.0</version>
<scope>system</scope>
<systemPath>${java.home}/jre/../lib/tools.jar</systemPath>
</dependency>
Hope this helped,
Roland
On Tuesday 06 June 2006 15:50, Rémy Sanlaville wrote:
> Hi,
>
> In the Maven's documentation, you can find the system scope :
> * system* - this scope is similar to provided except that you have to
> provide the JAR which contains it explicitly.
> The artifact is always available and is not looked up in
> a repository.
> cf.
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mech
>anism.html
>
> It is not mentionned nowhere else, even in the maven 2 book.
> I am wondering if this scope is usefull and when to use it.
> Did you have a good example for using this scope ?
>
> Best regards,
>
> Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
