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

Avoid 3rd party imports for Java Doc. #823

Merged
merged 1 commit into from
Feb 17, 2021

Conversation

michael-simons
Copy link
Contributor

One of our 3rd party dependencies, org.reactivestreams.Subscription, was imported just for a JavaDoc. This lead to a situation where the usage of the Config class needs the library on the classpath. We can avoid this by using a fully qualified import in the Javadoc.

I fixed the other 6 imports for consistency, even though they are from our own code.

I suggest cherrypicking this change into all maintained 4.x branches as well.

One of our 3rd party dependencies, `org.reactivestreams.Subscription`, was imported just for a JavaDoc. This lead to a situation where the usage of the `Config` class needs the library on the classpath. We can avoid this by using a fully qualified import in the Javadoc.

I fixed the other 6 imports for consistency, even though they are from our own code.
@michael-simons michael-simons merged commit 61767e8 into neo4j:4.3 Feb 17, 2021
@michael-simons michael-simons deleted the issue/fix-imports-4.3 branch February 17, 2021 12:47
michael-simons added a commit that referenced this pull request Feb 17, 2021
One of our 3rd party dependencies, `org.reactivestreams.Subscription`, was imported just for a JavaDoc. This lead to a situation where the usage of the `Config` class needs the library on the classpath. We can avoid this by using a fully qualified import in the Javadoc.

I fixed the other 6 imports for consistency, even though they are from our own code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants