how does classpath resolvement work with bundle imports vs package imports?

[jcompagner]

Hi,

i suddenly have a weird problem that the compile classpath which is resolved for a project, resolves to commons-io 2.2

[INFO] --- target-platform-configuration:2.7.5:target-platform (default-target-platform) @ j2db_server ---
[DEBUG] Configuring mojo org.eclipse.tycho:target-platform-configuration:2.7.5:target-platform from plugin realm ClassRealm[plugin>org.eclipse.tycho:target-platform-configuration:2.7.5, parent: jdk.internal.loader.ClassLoaders$AppClassLoader@5cb0d902]
[DEBUG] Configuring mojo 'org.eclipse.tycho:target-platform-configuration:2.7.5:target-platform' with basic configurator -->
[DEBUG]   (f) project = MavenProject: com.servoy:j2db_server:2023.3.0.3840_rc @ /var/lib/jenkins/jobs/master/jobs/server/workspace/j2db_server/pom.xml
[DEBUG] -- end configuration --
[DEBUG] Adding reactor project: MavenProject: com.servoy:j2db_log4j:2023.3.0.3840_rc @ /var/lib/jenkins/jobs/master/jobs/server/workspace/j2db_log4j/.tycho-consumer-pom.xml
[DEBUG] P2resolver.addMavenArtifact com.google.code.gson:gson:jar:2.9.1:compile
[DEBUG] P2Resolver: artifact com.google.code.gson:gson:2.9.1 at location /var/lib/jenkins/m2_master/com/google/code/gson/gson/2.9.1/gson-2.9.1.jar resolves installable unit com.google.gson/2.9.1
[DEBUG] P2resolver.addMavenArtifact com.google.guava:guava:jar:31.1-jre:compile
[DEBUG] P2Resolver: artifact com.google.guava:guava:31.1-jre at location /var/lib/jenkins/m2_master/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar resolves installable unit com.google.guava/31.1.0.jre
[DEBUG] P2resolver.addMavenArtifact com.google.guava:failureaccess:jar:1.0.1:compile
[DEBUG] P2Resolver: artifact com.google.guava:failureaccess:1.0.1 at location /var/lib/jenkins/m2_master/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar resolves installable unit com.google.guava.failureaccess/1.0.1
[DEBUG] P2resolver.addMavenArtifact com.google.guava:listenablefuture:jar:9999.0-empty-to-avoid-conflict-with-guava:compile
[INFO] Maven Artifact com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact com.google.code.findbugs:jsr305:jar:3.0.2:compile
[DEBUG] P2Resolver: artifact com.google.code.findbugs:jsr305:3.0.2 at location /var/lib/jenkins/m2_master/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar resolves installable unit org.jsr-305/3.0.2
[DEBUG] P2resolver.addMavenArtifact org.checkerframework:checker-qual:jar:3.12.0:compile
[DEBUG] P2Resolver: artifact org.checkerframework:checker-qual:3.12.0 at location /var/lib/jenkins/m2_master/org/checkerframework/checker-qual/3.12.0/checker-qual-3.12.0.jar resolves installable unit checker-qual/3.12.0
[DEBUG] P2resolver.addMavenArtifact com.google.errorprone:error_prone_annotations:jar:2.11.0:compile
[INFO] Maven Artifact com.google.errorprone:error_prone_annotations:2.11.0 is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact com.google.j2objc:j2objc-annotations:jar:1.3:compile
[INFO] Maven Artifact com.google.j2objc:j2objc-annotations:1.3 is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact jakarta.servlet:jakarta.servlet-api:jar:4.0.4:compile
[DEBUG] P2Resolver: artifact jakarta.servlet:jakarta.servlet-api:4.0.4 at location /var/lib/jenkins/m2_master/jakarta/servlet/jakarta.servlet-api/4.0.4/jakarta.servlet-api-4.0.4.jar resolves installable unit jakarta.servlet-api/4.0.0
[DEBUG] P2resolver.addMavenArtifact org.osgi:org.osgi.service.prefs:jar:1.1.2:compile
[DEBUG] P2Resolver: artifact org.osgi:org.osgi.service.prefs:1.1.2 at location /var/lib/jenkins/m2_master/org/osgi/org.osgi.service.prefs/1.1.2/org.osgi.service.prefs-1.1.2.jar resolves installable unit org.osgi.service.prefs/1.1.2.202109301733
[DEBUG] P2resolver.addMavenArtifact org.osgi:osgi.annotation:jar:8.0.1:compile
[DEBUG] P2Resolver: artifact org.osgi:osgi.annotation:8.0.1 at location /var/lib/jenkins/m2_master/org/osgi/osgi.annotation/8.0.1/osgi.annotation-8.0.1.jar resolves installable unit osgi.annotation/8.0.1.202109301733
[DEBUG] P2resolver.addMavenArtifact commons-fileupload:commons-fileupload:jar:1.4:compile
[DEBUG] P2Resolver: artifact commons-fileupload:commons-fileupload:1.4 at location /var/lib/jenkins/m2_master/commons-fileupload/commons-fileupload/1.4/commons-fileupload-1.4.jar resolves installable unit org.apache.commons.commons-fileupload/1.4.0
[DEBUG] P2resolver.addMavenArtifact commons-io:commons-io:jar:2.2:compile
[DEBUG] P2Resolver: artifact commons-io:commons-io:2.2 at location /var/lib/jenkins/m2_master/commons-io/commons-io/2.2/commons-io-2.2.jar resolves installable unit org.apache.commons.io/2.2.0
[DEBUG] Registered artifact repository org.eclipse.tycho.repository.registry.facade.RepositoryBlackboardKey(uri=file:/resolution-context-artifacts@%252Fvar%252Flib%252Fjenkins%252Fjobs%252Fmaster%252Fjobs%252Fserver%252Fworkspace%252Fj2db_server)

you see that after fileupload1.4 the commons-io 2.2 is added,
file upload has a package import "org.apache.commons.io".

But the thing is the j2db_server project it self also had that but with a version boundary:

org.apache.commons.io;version="2.8.0",

so it should have mapped to at least 2.8 not 2.2

if i change that package import to bundle import:

org.apache.commons.commons-io;bundle-version="2.8.0"

then suddenly it does resolve to 2.11 (not even 2.8)

[INFO] --- target-platform-configuration:2.7.5:target-platform (default-target-platform) @ j2db_server ---
[DEBUG] Configuring mojo org.eclipse.tycho:target-platform-configuration:2.7.5:target-platform from plugin realm ClassRealm[plugin>org.eclipse.tycho:target-platform-configuration:2.7.5, parent: jdk.internal.loader.ClassLoaders$AppClassLoader@5cb0d902]
[DEBUG] Configuring mojo 'org.eclipse.tycho:target-platform-configuration:2.7.5:target-platform' with basic configurator -->
[DEBUG]   (f) project = MavenProject: com.servoy:j2db_server:2023.3.0.3840_rc @ /var/lib/jenkins/jobs/master/jobs/server/workspace/j2db_server/pom.xml
[DEBUG] -- end configuration --
[DEBUG] Adding reactor project: MavenProject: com.servoy:j2db_log4j:2023.3.0.3840_rc @ /var/lib/jenkins/jobs/master/jobs/server/workspace/j2db_log4j/.tycho-consumer-pom.xml
[DEBUG] P2resolver.addMavenArtifact com.google.code.gson:gson:jar:2.9.1:compile
[DEBUG] P2Resolver: artifact com.google.code.gson:gson:2.9.1 at location /var/lib/jenkins/m2_master/com/google/code/gson/gson/2.9.1/gson-2.9.1.jar resolves installable unit com.google.gson/2.9.1
[DEBUG] P2resolver.addMavenArtifact com.google.guava:guava:jar:31.1-jre:compile
[DEBUG] P2Resolver: artifact com.google.guava:guava:31.1-jre at location /var/lib/jenkins/m2_master/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar resolves installable unit com.google.guava/31.1.0.jre
[DEBUG] P2resolver.addMavenArtifact com.google.guava:failureaccess:jar:1.0.1:compile
[DEBUG] P2Resolver: artifact com.google.guava:failureaccess:1.0.1 at location /var/lib/jenkins/m2_master/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar resolves installable unit com.google.guava.failureaccess/1.0.1
[DEBUG] P2resolver.addMavenArtifact com.google.guava:listenablefuture:jar:9999.0-empty-to-avoid-conflict-with-guava:compile
[INFO] Maven Artifact com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact com.google.code.findbugs:jsr305:jar:3.0.2:compile
[DEBUG] P2Resolver: artifact com.google.code.findbugs:jsr305:3.0.2 at location /var/lib/jenkins/m2_master/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar resolves installable unit org.jsr-305/3.0.2
[DEBUG] P2resolver.addMavenArtifact org.checkerframework:checker-qual:jar:3.12.0:compile
[DEBUG] P2Resolver: artifact org.checkerframework:checker-qual:3.12.0 at location /var/lib/jenkins/m2_master/org/checkerframework/checker-qual/3.12.0/checker-qual-3.12.0.jar resolves installable unit checker-qual/3.12.0
[DEBUG] P2resolver.addMavenArtifact com.google.errorprone:error_prone_annotations:jar:2.11.0:compile
[INFO] Maven Artifact com.google.errorprone:error_prone_annotations:2.11.0 is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact com.google.j2objc:j2objc-annotations:jar:1.3:compile
[INFO] Maven Artifact com.google.j2objc:j2objc-annotations:1.3 is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with <pomDependencies>wrapAsBundle</pomDependencies> in target platform configuration.
[DEBUG] P2resolver.addMavenArtifact jakarta.servlet:jakarta.servlet-api:jar:4.0.4:compile
[DEBUG] P2Resolver: artifact jakarta.servlet:jakarta.servlet-api:4.0.4 at location /var/lib/jenkins/m2_master/jakarta/servlet/jakarta.servlet-api/4.0.4/jakarta.servlet-api-4.0.4.jar resolves installable unit jakarta.servlet-api/4.0.0
[DEBUG] P2resolver.addMavenArtifact org.osgi:org.osgi.service.prefs:jar:1.1.2:compile
[DEBUG] P2Resolver: artifact org.osgi:org.osgi.service.prefs:1.1.2 at location /var/lib/jenkins/m2_master/org/osgi/org.osgi.service.prefs/1.1.2/org.osgi.service.prefs-1.1.2.jar resolves installable unit org.osgi.service.prefs/1.1.2.202109301733
[DEBUG] P2resolver.addMavenArtifact org.osgi:osgi.annotation:jar:8.0.1:compile
[DEBUG] P2Resolver: artifact org.osgi:osgi.annotation:8.0.1 at location /var/lib/jenkins/m2_master/org/osgi/osgi.annotation/8.0.1/osgi.annotation-8.0.1.jar resolves installable unit osgi.annotation/8.0.1.202109301733
[DEBUG] P2resolver.addMavenArtifact commons-fileupload:commons-fileupload:jar:1.4:compile
[DEBUG] P2Resolver: artifact commons-fileupload:commons-fileupload:1.4 at location /var/lib/jenkins/m2_master/commons-fileupload/commons-fileupload/1.4/commons-fileupload-1.4.jar resolves installable unit org.apache.commons.commons-fileupload/1.4.0
[DEBUG] P2resolver.addMavenArtifact commons-io:commons-io:jar:2.11.0:compile
[DEBUG] P2Resolver: artifact commons-io:commons-io:2.11.0 at location /var/lib/jenkins/m2_master/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar resolves installable unit org.apache.commons.commons-io/2.11.0
[DEBUG] Registered artifact repository org.eclipse.tycho.repository.registry.facade.RepositoryBlackboardKey(uri=file:/resolution-context-artifacts@%252Fvar%252Flib%252Fjenkins%252Fjobs%252Fmaster%252Fjobs%252Fserver%252Fworkspace%252Fj2db_server)
[INFO] 

any idea why that is?