[🐛 Bug]: Missing pom file for org.seleniumhq.selenium:selenium-devtools-v119:4.16.0

[dietzsch]

What happened?

We have seen that today a new version of Selenium 4.16.0 was released. When updating the Selenium version to 4.16.0 the build fails as the transitive dependency on org.seleniumhq.selenium:selenium-devtools-v119:4.16.0 can not be resolved. From what we can see on MavenCentral the jar file, javadoc are present, but the pom file is missing even when the checksum/signature for that file is available.

How can we reproduce the issue?

we have a Java project based on Gradle with a dependency like this:

    testImplementation "org.seleniumhq.selenium:selenium-java:4.16.0"

Relevant log output

* What went wrong:
Execution failed for task ':vmaas-password-encoder:compileTestGroovy'.
> Could not resolve all files for configuration ':vmaas-password-encoder:testCompileClasspath'.
   > Could not resolve org.seleniumhq.selenium:selenium-devtools-v119:4.16.0.
     Required by:
         project :vmaas-password-encoder > org.seleniumhq.selenium:selenium-java:4.16.0
      > Could not resolve org.seleniumhq.selenium:selenium-devtools-v119:4.16.0.
         > Could not get resource 'https://repo.spring.io/plugins-release/org/seleniumhq/selenium/selenium-devtools-v119/4.16.0/selenium-devtools-v119-4.16.0.pom'.
            > Could not GET 'https://repo.spring.io/plugins-release/org/seleniumhq/selenium/selenium-devtools-v119/4.16.0/selenium-devtools-v119-4.16.0.pom'. Received status code 401 from server: 
      > Could not resolve org.seleniumhq.selenium:selenium-devtools-v119:4.16.0.
         > Could not get resource 'https://repo.spring.io/release/org/seleniumhq/selenium/selenium-devtools-v119/4.16.0/selenium-devtools-v119-4.16.0.pom'.
            > Could not GET 'https://repo.spring.io/release/org/seleniumhq/selenium/selenium-devtools-v119/4.16.0/selenium-devtools-v119-4.16.0.pom'. Received status code 401 from server:

Operating System

CentOS

Selenium version

Selenium Java 4.16.0

What are the browser(s) and version(s) where you see this issue?

n/a

What are the browser driver(s) and version(s) where you see this issue?

n/a

Are you using Selenium Grid?

No response

[github-actions]

@dietzsch, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[asolntsev]

I am using a simple workaround - just exclude this dependency in my build.gradle:

dependencies {
    ...

    testImplementation("org.seleniumhq.selenium:selenium-java:4.16.0") {
      exclude group: 'org.seleniumhq.selenium', module: 'selenium-devtools-v119' // issue https://github.com/SeleniumHQ/selenium/issues/13256
    }

    ...
}

[github-actions]

This issue is looking for contributors.

Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.

[titusfortner]

Fixed in 4.16.1

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.