Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17310

Can't find jakarta.activation-api version jbossorg-1 in maven central

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 28.0.0.Beta1, 28.0.0.Final
    • 27.0.0.Final
    • BOM
    • None
    • ---
    • ---

      Can't find jakarta.activation-api version jbossorg-1 in maven central.

      <groupId>org.wildfly.bom</groupId>
      <artifactId>wildfly-ee-with-tools</artifactId>
      <version>27.0.0.Final</version>
      <type>pom</type>
      

      is available in without any special repositories specified. But some artifacts its depends on is not.

      The following do not build.

      	<dependencyManagement>
      		<dependencies>
      			<dependency>
      				<groupId>org.wildfly.bom</groupId>
      				<artifactId>wildfly-ee-with-tools</artifactId>
      				<version>27.0.0.Final</version>
      				<type>pom</type>
      				<scope>import</scope>
      			</dependency>
      		</dependencies>
      	</dependencyManagement>
      
      	<dependencies>
      		<dependency>
      			<groupId>jakarta.activation</groupId>
      			<artifactId>jakarta.activation-api</artifactId>
      		</dependency>
      	</dependencies>
      
      [ERROR] Failed to execute goal on project bom-problem-27: Could not resolve dependencies for project test:bom-problem-27:war:0.0.1-SNAPSHOT: Could not find artifact jakarta.activation:jakarta.activation-api:jar:2.1.1.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
      

      Adding the following repository it works, but should it be necessary?

      	<repositories>
      		<repository>
      			<id>jboss-public-maven-repository</id>
      			<url>https://repository.jboss.org/nexus/content/groups/public/</url>
      		</repository>
      	</repositories>
      

            yborgess1@redhat.com Yeray Borges Santana
            attiand Mattias Andersson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: