I agree with this : only "required for any use case" dependencies have
to be made non-optional. Without this, transitive dependencies is not a
cool feature anymore and becomes a "-hell".
Well, anything but core dependencies are IMHO optional.
If you decide to make usage of functionality, that
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
???
test
It will be used for the documentation
h
Emmanuel Bourg wrote on Thursday, March 23, 2006 12:59 PM:
> Carlos Sanchez wrote:
>> no, scope is different than optional
>>
>>
>> true
>>
>
> 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 wou
Carlos Sanchez wrote:
no, scope is different than optional
true
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 s
no, scope is different than optional
true
On 3/23/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Henri Yandell wrote on Thursday, March 23, 2006 9:14 AM:
>
> > How do you do that in m1?
> >
> >
> > optional
> >
>
> Exactly! The project.xml of configuration already have some deps with scop
Henri Yandell wrote on Thursday, March 23, 2006 9:14 AM:
> How do you do that in m1?
>
>
> optional
>
Exactly! The project.xml of configuration already have some deps with scope
definitions for test. Similar can be done for "optional".
- Jörg
How do you do that in m1?
optional
??
Hen
On 3/22/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm using maven2 and commons-configuration, and I need to configure
> lot's of as commons-configuration POM declares lot's of
> dependencies that are only required for some special
Hello,
I'm using maven2 and commons-configuration, and I need to configure
lot's of as commons-configuration POM declares lot's of
dependencies that are only required for some specialized use-cases.
Those dependencies may be declared as (dom4j, servletapi,
comons-codec...)
Could someone