Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no inclusion filter #102

Open
mhogerheijde opened this issue Feb 2, 2016 · 1 comment
Open

There is no inclusion filter #102

mhogerheijde opened this issue Feb 2, 2016 · 1 comment

Comments

@mhogerheijde
Copy link

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.

@dwijnand
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants