Github user metlos commented on the issue:
https://github.com/apache/tinkerpop/pull/494
Yes, Java makes it somewhat difficult to properly declare "module
boundaries" - let's hope Java 9 will do that right.
But for now, it is often useful to declare certain packages as internal and
not consider any changes in them as "user-facing". As shown with
`org.apache.tinkerpop.shaded`, it is quite easy to exclude packages from the
API check with Revapi.
If the internal and API classes are mixed within a single package, we could
also annotate the internal classes with some dedicated annotation - let's say
`org.apache.tinkerpop.Internal` and configure Revapi to ignore anything
annotated with that annotation. Revapi can also be configured to just ignore
certain classes but that's slightly more involved, because you'd need to modify
the POM each time you add an internal class (as opposed to just annotating the
class).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
