Ok,
Got subproject with source of class A,
and got subproject with source of class B,
Here are examples of the two classes:
import org.pack.B
publica class A{
private B;
...
}
import org.pack.A
publica class B{
private A;
}
As you can see, both are inter-dependent, but rest
You cannot :-(
Arnaud
On 1/22/07, fernando da Motta hildebrand [EMAIL PROTECTED]
wrote:
Ok,
Got subproject with source of class A,
and got subproject with source of class B,
Here are examples of the two classes:
import org.pack.B
publica class A{
private B;
...
}
import org.pack.A
I'm sorry but what I've found were recomendations to explicitly set every
dependence. I'll suppose that it's the last word.
-Mensaje original-
De: Jason van Zyl [mailto:[EMAIL PROTECTED]
Enviado el: sábado, 07 de febrero de 2004 0:00
Para: Maven Users List
Asunto: Re: Recursive
Hi!
I'd like to know if there is any elegant way to avoid defining the
dependencies of the dependencies.
E.g. My project depends on xdoclet but xdoclet depends on commons-logging
and commons-collections, so I must include dependencies to every xdoclet jar
and both commons jars
!-- XDoclet
downloaded and dealt with once.
Jose Gonzalez Gomez wrote:
Has Maven any way to specify nested or recursive dependencies? So
now you must be asking what the #$@ is a recursive dependency...
An example: I'm just beginning to play a bit with maven, and have
defined my first dependencies. I'm
To: Maven Users List
Subject: Re: Recursive dependencies
I agree with this.
Instead of having a huge long list of dependecies, it would be nice if
you could group dependecies. Using the Struts example below you could
have a maven structure like the following
dependency
:
Has Maven any way to specify nested or recursive dependencies? So
now you must be asking what the #$@ is a recursive dependency...
An example: I'm just beginning to play a bit with maven, and have
defined my first dependencies. I'm using Struts, so I thought I should
put Struts
