Custom Maven multi-module structure not persisted
Answered
I have a larger set of Maven projects which to some degree have sub-modules also. While importing all of these into the same project and defining a custom module grouping isn't a problem, these settings are not persisted and on importing/creating a new sub-module or restarting IntelliJ all the logically assigned groups are gone and all the projects are in the base structure (like after the import) again.
Is there a way to teach IntelliJ to keep my logical structure?
Please sign in to leave a comment.
Do you mean this: https://youtrack.jetbrains.com/issue/IDEA-139882 ?
Thanks for the link to the issue tracker. This seems to fix the problem of organizing multi-projects in a more meaningful way without losing the structure on any change. However, now IntelliJ IDEA does not recognize the source-, test- and resource-directories of multi-modul projects automatically. This is a pain when you deal with projects like Apache Camel (https://github.com/apache/camel) which has plenty (>100) of such sub-modules. Sure, manually fixing this could solve the issue, though for a project like Apache Camel this will last almost a day tweeking the settings.
I also noticed that on managing multi-maven projects that way, Maven dependencies are not specified for these projects. Again, manual tweaking is possible but as soon as you execute Maven/Reimport all these manually added dependencies are gone again.
Any tips on this issue are more than welcome. Currently this "fix" is more pain than not organizing projects logically ...