Wildfly ee bom giving errors on jbossorg versions for jakartaee10

Denis Golubovic

unread,

Feb 9, 2023, 4:36:23 AM2/9/23

to WildFly

Hi,

I am currently migrating our project to WF27 (27.0.1.Final) and jakartaEE10.

I am using these dependencies:

<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-ee</artifactId>
<version>27.0.1.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-ee-with-tools</artifactId>
<version>27.0.1.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>

together with:

<dependency>
<groupId>jakarta.platform</groupId>
<artifactId>jakarta.jakartaee-api</artifactId>
<version>${jakartaee-platform.version}</version>
<type>pom</type>
<scope>provided</scope>
</dependency>

We are getting errors for:
Failure to find jakarta.mail:jakarta.mail-api:jar:2.1.1.jbossorg-1
Failure to find jakarta.websocket:jakarta.websocket-api:jar:2.1.0-jbossorg-2
Failure to find jakarta.websocket:jakarta.websocket-client-api:jar:2.1.0-jbossorg-2
Failure to find jakarta.activation:jakarta.activation-api:jar:2.1.1.jbossorg-1

Checking in maven central there are no jbossorg versions. I tried to change the versions in wildfly-ee BOM by removing ".jbossorg-" and it worked.

What is the proper solution here? Should there be a change in wildfly-ee BOM versions for the above dependencies?

Br,
Denis

James Perkins

unread,

Feb 9, 2023, 4:39:46 AM2/9/23

to WildFly

Those were forked with patches. The only exist in the JBoss Nexus Repository. You'd need to add that repository to your pom.

<repositories>
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>

Eduardo Martins

unread,

Feb 9, 2023, 4:53:58 AM2/9/23

to Denis Golubovic, WildFly

Hi Dennis, besides James fix I have some comments about your project, please see inline.

On Thu, 9 Feb 2023 at 10:36, Denis Golubovic <deng...@gmail.com> wrote:

Hi,

I am currently migrating our project to WF27 (27.0.1.Final) and jakartaEE10.

I am using these dependencies:

<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-ee</artifactId>
<version>27.0.1.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-ee-with-tools</artifactId>
<version>27.0.1.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>

The EE-with-tools BOM extends the EE BOM so you may import only the EE-with-tools one.

together with:

<dependency>
<groupId>jakarta.platform</groupId>
<artifactId>jakarta.jakartaee-api</artifactId>
<version>${jakartaee-platform.version}</version>
<type>pom</type>
<scope>provided</scope>
</dependency>

Our BOMs should provide all the APIs needed to build/deploy/test/debug properly. When using 3rd party you may end up with at least wrong debug code lines.

If there is an API missing on our BOMs, that is included with WildFly, please let me know.

—E

Denis Golubovic

unread,

Feb 9, 2023, 5:32:53 AM2/9/23

to WildFly

Thank you both for quick feedback. I will have a look and get back if there are other issues.

Br,
Denis

Denis Golubovic

unread,

Feb 9, 2023, 5:53:40 AM2/9/23

to WildFly

Just to be clear, we are forced to use your nexus repository rather than maven central in order to get the bom to work properly?

We would like to have it locally in our nexus or in maven central. Is that possible?

Eduardo Martins

unread,

Feb 9, 2023, 6:04:19 AM2/9/23

to Denis Golubovic, WildFly

Any jboss specific version of third party artifacts are not mirrored to Maven Central so either you add our repo (please note you can specify first Maven central and that will prioritize it over ours), or you can mirror our artifacts to a local repo, but that would be a pain to maintain

—E

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/7dfced7e-2bce-4c2c-b8eb-cfa2215d47fdn%40googlegroups.com.

Rainer Hochreiter

unread,

Dec 30, 2023, 8:36:32 AM12/30/23

to WildFly

Hm,

I have the same issue!

In maven central there are these "-jbossorg-2" packages available (see https://mvnrepository.com/artifact/jakarta.websocket/jakarta.websocket-api/2.1.0-jbossorg-2) but maven tells that they were not found in https://repo.maven.apache.org/maven2

So should we use the 2.1.0 or 2.1.1 packages for web socket api?

Eduardo Martins

unread,

Jan 2, 2024, 5:18:56 AM1/2/24

to Rainer Hochreiter, WildFly

Hi Rainer, perhaps you don’t have the jboss.org public repo defined in the pom.xml, or in your ~/.m2/settings.xml ?

<id>jboss-public-maven-repository</id>

<name>JBoss Public Maven Repository</name>

<url>https://repository.jboss.org/nexus/content/groups/public/</url>

<updatePolicy>never</updatePolicy>

</releases>

<updatePolicy>never</updatePolicy>

</snapshots>

<layout>default</layout>

</repository>

</repositories>

<id>jboss-public-maven-repository</id>

<name>JBoss Public Maven Repository</name>

<url>https://repository.jboss.org/nexus/content/groups/public/</url>

</releases>

</snapshots>

</pluginRepository>

</pluginRepositories>

—E

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/e2c9b029-6f2f-4eee-8885-0c026629d7c0n%40googlegroups.com.

Reply all

Reply to author

Forward