Fix Quarkus platform BOM version info collection for analytics

[aloubyansky]

Pixes platform BOM info collection processing project's dependency version constraints

[rsvoboda]

LGTM and thanks for the fix @aloubyansky.

@brunobat about CUSTOM value of the version - will the version reports need to be adjusted to accommodate this addition or it will be transparent to them?

[aloubyansky]

I didn't start a separate discussion about this. CUSTOM is a suggestion. FYI @maxandersen

[brunobat]

I think CUSTOM is fine and will show up in the versions on future reports.
This change must not be back-ported because it will pollute previous data in the system, @gsmet, @aloubyansky

[gsmet]

This change must not be back-ported because it will pollute previous data in the system

I'm not sure I understand? For me, it's just make the reporting a bit more accurate but shouldn't pollute anything?

Could you clarify?

[aloubyansky]

Yeah, I am not sure about the risk of backporting. But if you don't like the CUSTOM change, backporting the main fix would make sense. I could create a dedicated PR for 3.15 in that case.

[brunobat]

Because data for existing back-ported versions will have a mix of N/A and CUSTOM that will clash with the previous logic of only having N/A, especially if we look to major.minor versions.
If we do it from now on, we will know that those versions data is always consistent.
We can backport, but we will need to filter by full version in the case of 3.15.x if we require consistent data...
... Or maybe we don't need to be that strict and just need understanding what's going on.

[brunobat]

Yeah, I am not sure about the risk of backporting. But if you don't like the CUSTOM change, backporting the main fix would make sense. I could create a dedicated PR for 3.15 in that case.

I like the CUSTOM, and it can be on a different PR.

[aloubyansky]

Just to clarify, @brunobat you would like me to remove the CUSTOM change from this one and add it in a separate PR?

[brunobat]

Yes, that way we can back-port the remaining changes without any concerns.

[aloubyansky]

The CUSTOM change is now in #45501

[brunobat]

Excellent! Thanks @aloubyansky

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 3e7ebdf.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.testing.KafkaDevServicesContinuousTestingWorkingAppPropsTestCase.testContinuousTestingScenario3 - History

• io.quarkus.builder.BuildException: Build failure: Build failed due to errors [error]: Build step io.quarkus.apicurio.registry.devservice.DevServicesApicurioRegistryProcessor\#startApicurioRegistryDevService threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed for image quay.io/apicurio/apicurio-registry-mem:2.4.2.Final at io.quarkus.apicurio.registry.devservice.DevServicesApicurioRegistryProcessor.startApicurioRegistryDevService(DevServicesApicurioRegistryProcessor.java:90) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:732) at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856) - java.lang.RuntimeException

java.lang.RuntimeException: 
io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.apicurio.registry.devservice.DevServicesApicurioRegistryProcessor#startApicurioRegistryDevService threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed for image quay.io/apicurio/apicurio-registry-mem:2.4.2.Final
	at io.quarkus.apicurio.registry.devservice.DevServicesApicurioRegistryProcessor.startApicurioRegistryDevService(DevServicesApicurioRegistryProcessor.java:90)
	at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:732)
	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856)
	at io.quarkus.builder.BuildContext.run(BuildContext.java:256)
	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)

📦 integration-tests/grpc-hibernate

✖ com.example.grpc.hibernate.BlockingRawTest.shouldAdd - History

• Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at com.example.grpc.hibernate.BlockingRawTestBase.shouldAdd(BlockingRawTestBase.java:59)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)

---

⚙️ JVM Tests - JDK 17 Windows

📦 integration-tests/opentelemetry-quickstart

✖ io.quarkus.it.opentelemetry.OpenTelemetryDisabledTest.buildTimeDisabled - History

• Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryDisabledTest was not fulfilled within 200 milliseconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryDisabledTest was not fulfilled within 200 milliseconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at io.quarkus.it.opentelemetry.OpenTelemetryDisabledTest.buildTimeDisabled(OpenTelemetryDisabledTest.java:29)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)