quarkus: Quarks 3.3.1 & Gradle app stopped building due to missing mvnpm

Describe the bug

Our previously building and running Quarkus application using 3.3.1 has suddenly started failing to build (in the last week or so) due to a missing mvnpm listed in the BOM. The application is not using this and it is not using any extension (that I know of) that would use this.

Here’s the Gradle failure:

> Could not resolve all files for configuration ':cloud-common:quarkusProdRuntimeClasspathConfigurationDeployment'.
   > Could not find any version that matches org.mvnpm.at.vaadin:component-base:[24.1.12,24.2).
     Versions that do not match:
       - 24.2.2
       - 24.2.1
       - 24.2.0
       - 24.1.11
       - 24.1.10
       - + 15 more
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/mvnpm/at/vaadin/component-base/maven-metadata.xml
     Required by:
         project :cloud-common > io.quarkus.platform:quarkus-bom:3.3.1 > org.mvnpm.at.vaadin:app-layout:24.1.4 > org.mvnpm.at.vaadin:a11y-base:24.1.12

Just to be clear we have made no changes to the application or build files. It just doesn’t build any longer.

Expected behavior

That our application builds correctly, as it did before.

Actual behavior

Application fails to build.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

openjdk version “17.0.6” 2023-01-17

Quarkus version or git rev

3.3.1

Build tool (ie. output of mvnw --version or gradlew --version)

8.3

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 21 (20 by maintainers)

Most upvoted comments

Your suggestion works as well. Thanks!