Handle circular dependencies between modules
Any plans to support this in Demetra? I know, I shouldn't do that and blah blah blah... but when you're the only guy using IDEA, surrounded by a dozen users of that other IDE named after an astronomical event, things aren't that easy.
You-know-which IDE happily lets it's users declare circular dependencies between modules (er, projects), and after half an year, there are way too many dependencies, making it impossible for me to just refactor them out.
This is an old request, originally tracked as SCR #32407[/url], but apparently lost on the transition to Jira. Any updates about this?
Please sign in to leave a comment.
Err, IMHO Irida already supports this?!
It gives a warning during configuration, but it works.
Or are we talking about different things here?
Well, we have several module groupss with circular dependencies in our
code and it works with IDEA 5.1. Could you please provide more details
on what is not working in your environment?
Marcus Brito wrote:
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Hmm... it's been sometime since I last worked on a project with circular dependencies, so maybe I really forgot about it being supported in IDEA (heck, I'm the one who filed the original SCR).
Are there limitations on what kind of modules can have circular dependencies? Just before posting this, I tried marking an EJB module and a regular Java module as dependent on each other, but IDEA wouldn't let me, saying something like "Cyclic dependencies between J2EE modules 'EJBModule' and 'PlainJavaModule' are now allowed".
Two cups of coffee later, my memory is finally coming back. Circular dependencies are supported, as long as J2EE modules are not involved in the game. So... any plans of lifting this restriction for Demetra?
Sure.
Still the ball is on your side, I mean the request to jira of course=)
Here you go:
http://www.jetbrains.net/jira/browse/IDEA-6419