You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Achim Nierbeck <ac...@ptv.de> on 2010/10/06 10:27:50 UTC
Re: Definition of 'cycling' dependencies
I'd say like with classes you have feature set A which depends on feature set
B which itself depends on feature set C and this one is dependent on A
again. :), make sure you have more like a tree structure.
Mike Van wrote:
>
> In section 4.6 of the Karaf documentation there is a note to be careful
> when using features because of a risk of 'cycling' dependencies. Can
> someone describe what 'cycling' dependencies is, and how to avoid it?
>
> v/r,
>
> Mike Van
>
--
View this message in context: http://karaf.922171.n3.nabble.com/Definition-of-cycling-dependencies-tp1638007p1641156.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Definition of 'cycling' dependencies
Posted by Guillaume Nodet <gn...@gmail.com>.
Yeah, i guess we should make sure not to start an infinite loop at least.
Not sure what the current behavior is ...
On Wed, Oct 6, 2010 at 10:27, Achim Nierbeck <ac...@ptv.de> wrote:
>
> I'd say like with classes you have feature set A which depends on feature
> set
> B which itself depends on feature set C and this one is dependent on A
> again. :), make sure you have more like a tree structure.
>
>
> Mike Van wrote:
> >
> > In section 4.6 of the Karaf documentation there is a note to be careful
> > when using features because of a risk of 'cycling' dependencies. Can
> > someone describe what 'cycling' dependencies is, and how to avoid it?
> >
> > v/r,
> >
> > Mike Van
> >
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Definition-of-cycling-dependencies-tp1638007p1641156.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com