• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Circular dependency in RAD 7.0

 
Dash Abhisek
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am trying to migrate an ear from wsad 5.1 to rad 7.0 environment.I was getting a circular dependency because of which building of projects couldn't be carried out I circumvented the problem by changing the settings of RAD .But, as my migrated code will be eventually be running in some other instance of RAD this setting will not be of help .Does anyone has any idea how to get out of error due to circular dependency?


Thanks & Regards,
Abhisek
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34686
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Abhisek,
Get rid of the dependency. If you have control over the code, extract the lower level code into a separate project.
 
Dash Abhisek
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Jeanne,

Thanks fo the reply actually I went for those settings because of the reason that I am not very sure of what basically a circular dependency is all about,for me if project A has project B checked in Project References and Project B has Project A checked in Project references then it is a circular dependency but in my case the situation is quite different.

Project A is dependent upon Project B,Poject C and Project D.

Project B and C are not dependent upon any project.

Project D depends again upon Project B and Project C

Does this situation qualify as a circular dependency.

Please suggest how to remove the dependency.

Thanks & Regards,
Abhisek
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34686
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No that's not a circular dependency. There are two non circular paths.
A > D > B >C or A > D > C > B

There are two possibilities here:
1) There is another dependency. (This is likely - I recommend you double check - make sure you are looking at the projects build path and not just the project references.)
2) RAD is confused. Try forcing a "clean" project on B and C and then rebuild the whole workspace.
 
Dash Abhisek
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Jeanne,

Thanks a lot for the advice. I will let you know once I get back to code.I now feel basically this (circular dependency)is an error because the compiler is getting confused which project to compile first and which to compile second,am I right?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic