You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking for the possibility to have MiMa only report about specific packages that I declare to be "the public API" of my .jar file. Ultimately I would like to use the export and provides keywords from a module-info.java file to check only those classes contained within those packages.
Maybe I'm doing something wrong, but I seem to be able to have an exclusion filter, but not an inclusion filter. For now I have to exclude all packages that I don't consider part of the API and need to keep in mind that when adding a new package, it should be added to the exclusion filter as well.
The text was updated successfully, but these errors were encountered:
I think until MiMa gains support for deriving the packages from module-info.java having only an exclusion filter is the right API to expose. While everything is publically available (i.e. before JPMS) the burden should be on opt-in out.
I'm looking for the possibility to have MiMa only report about specific packages that I declare to be "the public API" of my .jar file. Ultimately I would like to use the
export
andprovides
keywords from amodule-info.java
file to check only those classes contained within those packages.Maybe I'm doing something wrong, but I seem to be able to have an exclusion filter, but not an inclusion filter. For now I have to exclude all packages that I don't consider part of the API and need to keep in mind that when adding a new package, it should be added to the exclusion filter as well.
The text was updated successfully, but these errors were encountered: