This repository was archived by the owner on Jun 26, 2026. It is now read-only.
Repository navigation
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
If resources of a module are placed in a top-level folder which can be interpreted as a valid java package name, then this will result in a split package error if a second module contains the same folder and both modules are used together in one project. A typical example of such a case is when you place icons that you use throughout your code into a top-level folder
icons. To avoid this problem I always use a name likeapp-iconsfor such a folder because that is not a valid java package name and so does not pose a problem. The most annoying aspect is that you will only notice this bug in a module when you use a second one with the same problem. It would be nice to have a checker which can explicitly examine modules for potential problems of this kind.All reactions