Maven Support (Bugs?) in IntelliJ 9 + more annoyances

Hi all,

I've just migrated to IntelliJ 9 Beta, and I'm trying to import a Maven project I've been working on, which consists of multiple modules with submodules. IntelliJ always could import these projects successfully, but currently, the project is not workable anymore, because of the following reasons:

1) all the dependencies are thrown together in one big pile, instead of per module. Now I cannot see which module has which dependency.
2) the project view has been changed in a way that I need much more navigation. It seems like the grouping of modules doesn't work anymore, and instead of showing the project structure, IntelliJ shows my directory structure.

One a sidenote, I've also noticed that pressing the left arrow in the project view doesn't work anymore. Normally, I would select a class, and if I would press the left button, the project navigator would go one level up. Currently, it doesn't work anymore: I first have to move up, to the package name, and then move left. Quite annoying, navigating this way is much slower than in IntelliJ8!

Thanks,

Erik



Attachment(s):
IntelliJ 9.png
IntelliJ 8.png
9 comments
Comment actions Permalink

2) the project view has been changed in a way that I need much more navigation. It seems like the grouping of modules doesn't work anymore, and instead of showing the project structure, IntelliJ shows my directory structure.


I have to say this was one of the best changes in Maia. My directory structure is usually well organized already, and I always struggled to keep that organization (or give up) on previous releases. Respecting (and displaying the contents) of my directory structures is a great improvement, imo.

0
Comment actions Permalink

Interesting. Have you taken a look at the screenshots? In my case, the structure is totally unusable and requires much more effort to navigate. It's actually a blocker for me, just like the project dependencies.

Btw, my directory structures are also well organized (they just use the maven convention, plus I use structures like:

main project
+ sub project
+-- sub project module
+-- sub project module

+ sub project
+-- sub project module
+-- sub project module

I'd like to have IntelliJ (9!) to represent this, just like it did before!)

0
Comment actions Permalink

Interesting. Have you taken a look at the screenshots? In my case, the structure is totally unusable and requires much more effort to navigate. It's actually a blocker for me, just like the project dependencies.


No, I didn't. I wasn't trying to demerit your problem, it's your problem, after all. If it bothers you, by all means, complain about it. I was just trying to provide a view that this change has indeed been positive for some of us.

... that being said, I've now taken a look at your screenshot, and get what you mean. Your project root seems to reside a couple levels above the directories you really work with, so it's a lot of extra navigation. Do you really work at all those projects at the same time? Maybe breaking this into multiple IDEA projects rooted further down your directory structure would provide a saner environment.

0
Comment actions Permalink

I agree that removing the module grouping in the project view is a huge step backwards. We have nearly 300 modules in our project, and having them in a big list is totally unmanageable. I don't actually navigate much in that view, but when I did briefly while trying Maia it was really painful. I'm using Maia at home for personal projects and for small projects obviously it's not an issue, but at work it kills me.

0
Comment actions Permalink

Hello Colin,

Why don't you re-layout the file system structure to be more manageable?
The layout of the IDEA project view (whatever algorithm we use for that)
is IDEA specific, and a clean layout of the file system will help all apps.

I agree that removing the module grouping in the project view is a
huge step backwards. We have nearly 300 modules in our project, and
having them in a big list is totally unmanageable. I don't actually
navigate much in that view, but when I did briefly while trying Maia
it was really painful. I'm using Maia at home for personal projects
and for small projects obviously it's not an issue, but at work it
kills me.


--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Marcus,

Thanks for looking at the screenshots and trying to understand the issue. To be honest: this is a really small project, consisting of 4 related projects, grouped in 1 IntelliJ project, where each project has 3 or 4 modules. It would be really unworkable to move this into multiple IDEA projects, since some of the modules are shared making refactoring sort of impossible, and other projects are more loosely coupled by an XML interface, but changes to that interface need to be reflected in all projects too... so no, splitting them would not be an option for me. Besides that, I find that having multiple IntelliJ instances in MacOS is really a pain.

So I think I'll keep complaining a bit ;-)

0
Comment actions Permalink

I can image. If the grouping would be lost, we would be on par with Eclipse, which also lacks grouping, and I think one of the big benefits is to have this grouping. I use the project navigator quite a lot, so this change has quite a strong impact on me. I also tried IntelliJ for smaller projects btw, and for that it wasn't an issue at all. But for my professional usage, it's unworkable, and I'll stick to 8 until it's resolved.

0
Comment actions Permalink

Hi Dmitry,

Well, I could, but it's a fairly huge job. It's a big project, we have in-house build tools that rely on this layout, etc. Plus the current layout is pretty easy to understand, everything is under <module name>/<version>/<module contents>. It makes grepping easy, and a lot of source code manipulations are easier because everything is at the same depth from the root.

I also think that philosophically one of the things I like best about IntelliJ's project setup (as compared to Eclipse or Maven) is that it's always been very flexible about how I lay my projects out. I hate having to restructure a project because of the whims of the tool I'm using. I guess having module groups seems like a pretty minimal piece of functionality that greatly improves this flexibility, especially since that support has always been there.

Cheers,
Colin

0
Comment actions Permalink

Hi,

I've replied in the neighbour thread: http://www.jetbrains.net/devnet/message/5249925#5249925.
Please share your opinion there.

Thanks,
Anton Makeev

0

Please sign in to leave a comment.