The documentation about scopes is defined here :
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
In maven 1, even if we don't use the scope for dependencies, you can define
them with
<dependency>
<groupId>???</groupId>
<artifactId>????</artifactId>
<version>????</version>
<properties>
<scope>test</scope>
</properties>
</dependency>
It will be used for the documentation
http://maven.apache.org/maven-1.x/dependencies.html
and to convert the m1 pom to the m2 pom in the repository
http://mavenbook.xwiki.com/xwiki/bin/view/Main/BeMaven2Friendly
cheers
Arnaud
On 3/23/06, Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
>
> Carlos Sanchez wrote:
> > no, scope is different than optional
> >
> > <properties>
> > <optional>true</optional>
> > </properties>
>
> What is the definition of an optional dependency ? It depends on the use
> of the library. If I use a plist configuration most of the time I would
> not want the commons-codec dependency to be excluded for example.
>
> There are several dependency sets depending on the features you are
> interested in as described here:
>
> http://jakarta.apache.org/commons/configuration/dependencies.html
>
> It's not obvious to decide what is optional imho.
>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
