Remove internal modules when they aren't referenced any longer #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a dependency management framework like Ivy, Maven or Gradle are used, you usually want them to do the dependency management completely.
It includes the management of the dependencies between internal modules, too. At the moment, IvyIDEA identifies dependency relations between internal modules, correctly, but it doesn't remove no longer existing dependency relations between internal modules. Leading to a total mess of deprecated module references.
You usually don't expect this behaviour. IntelliJ IDEA informs you, too, that manually made changes are lost after syncing again with Gradle or Maven enabled. IvyIDEA should behave the same way.
References to issue #165