|
| Re: Cyclic dependency [message #32942 is a reply to message #32611] |
Fri, 14 November 2008 16:54   |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 11/14/2008 4:16 AM, Naag wrote:
> Hi
> I would like to know about plugin cyclic dependency? How to solve this
> cyclic dependency with an example.
>
> please provide me a simple exmaple with two plugins.
I'm not sure what kind of example you're expecting. Any two plugins that
don't depend on each other is an example of avoiding a cyclic dependency.
The way to "solve" a cyclic dependency between PluginA and PluginB is to
NOT make PluginA depend on PluginB if PluginB already depends on
PluginA. It's a pretty simple rule.
If you want more help than that you'll have to provide more detail about
what you're trying to do (for example, why do both of your plugins
depend on each other).
Eric
|
|
|
|
| Re: Cyclic dependency [message #33224 is a reply to message #33155] |
Mon, 17 November 2008 06:56 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Naag,
you should rethink your architecture -
as Eric already asks you: WHY do you need this cyclic dependency
if you're the owner of plug-in a and b then you should find a way
without cyclic dependencies - perhaps using a third plug-in C or
re-structuring the content of your plug-ins or use of fragments
if there's really no way without these cyclic dependencies perhaps
eclipse-buddy is the way to go
ekke
Naag schrieb:
> Hi Eric
>
> Thanks for the response.
>
> All i need is to access the methods and variables of PLUG-IN A in
> PLUG-IN B and PLUG-IN B in PLUG-IN A.(Communication between two plugins).
>
> Also i would like to request to let me know about dependency and
> extension point if provided with an example.
>
> Regards
> Naag
>
>
|
|
|
|
| Re: Cyclic dependency [message #33512 is a reply to message #33259] |
Mon, 17 November 2008 15:09 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Naag schrieb:
> HI ekke
>
> There is no way restructure my architecture. I want to know about
> eclipse buddy policy. It will be a great help if u explain me buddy
> policy with a simple example.
>
> I am awaiting for your response.
>
> Regards
> Naag
>
theres a good article from alex blewitt:
http://www.eclipsezone.com/articles/eclipse-vms/
ekke
|
|
|
|
| Re: Cyclic dependency [message #33715 is a reply to message #33544] |
Mon, 17 November 2008 16:00 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Tom Schindl schrieb:
> Where's the reason to split 2 things into 2 bundles if they can't live
> without each other.
>
thats also my question to Naaq,
I understand that - with 3rd party bundles - there are situations you
have to use buddies or dynamic imports
But with bundles "under own control" there's always a way without cycles
ekke
> Extract the things of A and B which need each other in C and make A and
> B depend on C or if everything needs everything then move everything in
> one plugin.
>
> Tom
>
> ekke schrieb:
>> Naag schrieb:
>>> HI ekke
>>>
>>> There is no way restructure my architecture. I want to know about
>>> eclipse buddy policy. It will be a great help if u explain me buddy
>>> policy with a simple example.
>>>
>>> I am awaiting for your response.
>>>
>>> Regards
>>> Naag
>>>
>> theres a good article from alex blewitt:
>> http://www.eclipsezone.com/articles/eclipse-vms/
>>
>> ekke
>
>
|
|
|
|
|
| Re: Cyclic dependency [message #585317 is a reply to message #33155] |
Mon, 17 November 2008 06:56 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Naag,
you should rethink your architecture -
as Eric already asks you: WHY do you need this cyclic dependency
if you're the owner of plug-in a and b then you should find a way
without cyclic dependencies - perhaps using a third plug-in C or
re-structuring the content of your plug-ins or use of fragments
if there's really no way without these cyclic dependencies perhaps
eclipse-buddy is the way to go
ekke
Naag schrieb:
> Hi Eric
>
> Thanks for the response.
>
> All i need is to access the methods and variables of PLUG-IN A in
> PLUG-IN B and PLUG-IN B in PLUG-IN A.(Communication between two plugins).
>
> Also i would like to request to let me know about dependency and
> extension point if provided with an example.
>
> Regards
> Naag
>
>
|
|
|
|
| Re: Cyclic dependency [message #585450 is a reply to message #33259] |
Mon, 17 November 2008 15:09 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Naag schrieb:
> HI ekke
>
> There is no way restructure my architecture. I want to know about
> eclipse buddy policy. It will be a great help if u explain me buddy
> policy with a simple example.
>
> I am awaiting for your response.
>
> Regards
> Naag
>
theres a good article from alex blewitt:
http://www.eclipsezone.com/articles/eclipse-vms/
ekke
|
|
|
|
| Re: Cyclic dependency [message #585526 is a reply to message #33544] |
Mon, 17 November 2008 16:00 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Tom Schindl schrieb:
> Where's the reason to split 2 things into 2 bundles if they can't live
> without each other.
>
thats also my question to Naaq,
I understand that - with 3rd party bundles - there are situations you
have to use buddies or dynamic imports
But with bundles "under own control" there's always a way without cycles
ekke
> Extract the things of A and B which need each other in C and make A and
> B depend on C or if everything needs everything then move everything in
> one plugin.
>
> Tom
>
> ekke schrieb:
>> Naag schrieb:
>>> HI ekke
>>>
>>> There is no way restructure my architecture. I want to know about
>>> eclipse buddy policy. It will be a great help if u explain me buddy
>>> policy with a simple example.
>>>
>>> I am awaiting for your response.
>>>
>>> Regards
>>> Naag
>>>
>> theres a good article from alex blewitt:
>> http://www.eclipsezone.com/articles/eclipse-vms/
>>
>> ekke
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04778 seconds
] 
Search
Help
Register
Login
Home
