WildFly 40.0.0.Final build failure: unresolved org.osgi.service:org.osgi.service.prefs in wildfly-ejb-client-bom-builder

[Shalini kuruba]

Description

A clean build of WildFly 40.0.0.Final fails during BOM generation.

The failure occurs in:

wildfly-ejb-client-bom-builder

while executing:

org.wildfly.plugins:wildfly-bom-builder-plugin:2.0.10.Final:build-bom

Environment

• WildFly: 40.0.0.Final
• Maven: 3.9.9
• Java: 17
• Linux

Build Command

mvn clean install -Dcheckstyle.skip=true

Error

Failed to execute goal
org.wildfly.plugins:wildfly-bom-builder-plugin:2.0.10.Final:build-bom
on project wildfly-ejb-client-bom-builder

No versions available for
org.osgi.service:org.osgi.service.prefs:jar:[1.1.0,1.2.0)
within specified range

Dependency Chain

org.jboss.hal:hal-console
-> org.jboss.hal:hal-ballroom
-> org.jboss.hal:hal-dmr
-> org.jboss.hal:hal-config
-> org.gwtproject:gwt-dev:2.13.0
-> org.eclipse.jdt:org.eclipse.jdt.core:3.33.0
-> org.eclipse.platform:org.eclipse.core.resources:3.18.200
-> org.eclipse.platform:org.eclipse.core.expressions:3.8.200
-> org.eclipse.platform:org.eclipse.core.runtime:3.12.0
-> org.eclipse.platform:org.eclipse.equinox.preferences:3.10.0
-> org.osgi.service:org.osgi.service.prefs:[1.1.0,1.2.0)

Additional Investigation

The POM for org.eclipse.equinox.preferences:3.10.0 declares:

org.osgi.service org.osgi.service.prefs [1.1.0,1.2.0)

However, Maven Central appears not to contain artifacts under:

org.osgi.service:org.osgi.service.prefs

For example:

https://repo.maven.apache.org/maven2/org/osgi/service/org.osgi.service.prefs/1.1.1/

returns 404.

Can someone confirm whether additional repositories are required or whether this is a known issue with 40.0.0.Final?

[Brian Stansberry]

Hello,

That artifact should be in Maven Central:

https://repo1.maven.org/maven2/org/osgi/org.osgi.service.prefs/1.1.1/

I don't know why the repo.maven.apache.org URL doesn't work.

That said, to build WildFly you must have JBoss Nexus available: https://repository.jboss.org/nexus/repository/public/

That doesn't seem relevant to what you are experiencing though. JBoss Nexus does not provide that artifact, so if the build is pulling it, it gets it from Maven Central.

[Brian Stansberry]

Sorry; I realize now that the Maven Central link I posted was for a different groupId -- org.osgi not org.osgi.service.

https://mvnrepository.com/artifact/org.osgi.service/org.osgi.service.prefs/1.1.1 shows the Repository for the groupId you posted as only being the 'Logical Hacking' repo at https://artifacts.logicalhacking.com/maven3/

When I build that module I don't have this problem and the build pulls down org.osgi:org.osgi.service.prefs:1.1.1 (and 1.1.2).

[Shalini kuruba]

Thanks for checking Brian. I see that your build successfully resolves org.osgi:org.osgi.service.prefs:1.1.1 (and 1.1.2).

In my environment, the dependency declaration in org.eclipse.equinox.preferences references:

<groupId>org.osgi.service</groupId> <artifactId>org.osgi.service.prefs</artifactId> <version>[1.1.0,1.2.0)</version>

Since I cannot find org.osgi.service:org.osgi.service.prefs in Maven Central, could you clarify how the build resolves this dependency successfully? Is there a relocation, dependency management rule, or additional repository involved that causes Maven to resolve it as org.osgi:org.osgi.service.prefs?

[Brian Stansberry]

I don't know for sure what specific dependency tree results in it being pulled down. It's not obvious from mvn -X -e output.

I deleted the entire org/eclipse tree from my local repo and built the the boms/user/client/ejb-client module. A number of versions of the org.eclipse.equinox.preferences artifact are pulled down but none reference groupId org.osgi.service. That string only appears in artifactIds:

$ cd ~/.m2/repository/org/eclipse/platform/org.eclipse.equinox.preferences/
$ grep -r org\.osgi\.service
./3.10.1/org.eclipse.equinox.preferences-3.10.1.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.10.200/org.eclipse.equinox.preferences-3.10.200.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.11.200/org.eclipse.equinox.preferences-3.11.200.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.11.100/org.eclipse.equinox.preferences-3.11.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.10.100/org.eclipse.equinox.preferences-3.10.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.12.100/org.eclipse.equinox.preferences-3.12.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.12.0/org.eclipse.equinox.preferences-3.12.0.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.10.400/org.eclipse.equinox.preferences-3.10.400.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.11.400/org.eclipse.equinox.preferences-3.11.400.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.11.0/org.eclipse.equinox.preferences-3.11.0.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.10.300/org.eclipse.equinox.preferences-3.10.300.pom:      <artifactId>org.osgi.service.prefs</artifactId>
./3.11.300/org.eclipse.equinox.preferences-3.11.300.pom:      <artifactId>org.osgi.service.prefs</artifactId>

I then grepped my entire local repo and nothing has that groupId.

[Shalini kuruba]

Hi Brian,

The dependency org.osgi.service:org.osgi.service.prefs originates from org.eclipse.equinox.preferences-3.10.0.pom

[eclipse/platform/org.eclipse.equinox.preferences]$ grep -r org\.osgi\.service
3.10.0/org.eclipse.equinox.preferences-3.10.0.pom:      <groupId>org.osgi.service</groupId>
3.10.0/org.eclipse.equinox.preferences-3.10.0.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.10.1/org.eclipse.equinox.preferences-3.10.1.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.10.100/org.eclipse.equinox.preferences-3.10.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.10.200/org.eclipse.equinox.preferences-3.10.200.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.10.300/org.eclipse.equinox.preferences-3.10.300.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.10.400/org.eclipse.equinox.preferences-3.10.400.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.11.0/org.eclipse.equinox.preferences-3.11.0.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.11.100/org.eclipse.equinox.preferences-3.11.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.11.200/org.eclipse.equinox.preferences-3.11.200.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.11.300/org.eclipse.equinox.preferences-3.11.300.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.11.400/org.eclipse.equinox.preferences-3.11.400.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.12.0/org.eclipse.equinox.preferences-3.12.0.pom:      <artifactId>org.osgi.service.prefs</artifactId>
3.12.100/org.eclipse.equinox.preferences-3.12.100.pom:      <artifactId>org.osgi.service.prefs</artifactId>

[Brian Stansberry]

Building WildFly doesn't bring in org.eclipse.equinox.preferences:3.10.0 for me, and I've not heard of any WF developers or our CI systems having problems.

In my maven repo various versions of org.eclipse.core.runtime declare a range version of [3.10.0,4.0.0) for org.eclipse.equinox.preferences, so I could see how 3.10.0 would get pulled down, but it doesn't happen for me.

We don't have direct dependencies on org.eclipse.core.runtime or org.eclipse.equinox.preferences, so we have no control over this.

I will say though that I don't see any org.eclipse.equinox.preferences:3.10.0  in Maven Central:

https://central.sonatype.com/artifact/org.eclipse.platform/org.eclipse.equinox.preferences/versions

So maybe your maven settings are resulting in it getting pulled down from somewhere else? Or perhaps it's just in your local maven repo from some other build, and since it's there it's being used? Perhaps just delete it from your local repo?

Other than that, sorry, I don't know how to help here.