Hi Marco,
It is very simple. Maven stops searching for the dependency when it finds
provided scope and maven assumes the dependency will be provided
externally. Best example being server library jars like servlet-api jar.
Below link will give you clear picture
Hi
thanks for your reply... I read the maven dependency mechanism and I
understud how it's works...
The definition of 'provided' scope is that is only available on the
compilation and test classpath and the user should provide the
dependency at runtime.
And the definition of 'runtime' scopoe is
On 18/07/2012 12:23 PM, Marco Speranza wrote:
Hi
thanks for your reply... I read the maven dependency mechanism and I
understud how it's works...
The definition of 'provided' scope is that is only available on the
compilation and test classpath and the user should provide the
dependency at
Hi Ron...
yes I understood your point.. but some days ago I tried to compile a
project like this:
prj.a:
public class A extends B{}
prj.b:
public class B extends C{}
prj.c:
public class C{}
where their pom are:
prj.a - prj.b (provided scope)
prj.b - prj.c (provided scope)
is strange...
Hi all...
a friend of mine and I have experienced a compilation error when we
have tried to compile this project:
prj.a:
public class A extends B{}
prj.b:
public class B extends C{}
prj.c:
public class C{}
where their pom are:
prj.a - prj.b (provided scope)
prj.b - prj.c (provided scope)
