We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When building Selenium with latest we are getting an invalid Automatic-Module-Name: com.graphql-java in the manifest.
invalid Automatic-Module-Name: com.graphql-java
There are two problems with that:
The better name is probably something like com.graphql.dataloader or similar
To get around this you just need to update gradle config to do what the Gradle docs suggests
To Reproduce Update https://github.com/SeleniumHQ/selenium/blob/e92b16f0832da62204bda5d01fbc430ec9401deb/java/maven_deps.bzl to latest.
And then run bazel build grid in a terminal
bazel build grid
The text was updated successfully, but these errors were encountered:
Fix invalid Automatic-Module-Name
0ed4f2e
Consistent with https://github.com/graphql-java/graphql-java/pull/2423/files Fixes graphql-java#101
87573f8
Successfully merging a pull request may close this issue.
Describe the bug
When building Selenium with latest we are getting an
invalid Automatic-Module-Name: com.graphql-java
in the manifest.There are two problems with that:
The better name is probably something like com.graphql.dataloader or similar
To get around this you just need to update gradle config to do what the Gradle docs suggests
To Reproduce
Update https://github.com/SeleniumHQ/selenium/blob/e92b16f0832da62204bda5d01fbc430ec9401deb/java/maven_deps.bzl to latest.
And then run
bazel build grid
in a terminalThe text was updated successfully, but these errors were encountered: