Make sure GraalVM js artifact is consistent with the SDK version

[gsmet]

Related to quarkusio/quarkus-platform#707

[ppalaga]

@gsmet thanks, this makes the life of Camel Quarkus easier in the community, but IIRC, org.graalvm.js:js is not available on Mandrel (cc @zakkak @galderz ). If that's really the case this will make the life of the prod team harder. Note that the js-dsl extension is not supported in CEQ product currently and will hardly be in the future because of the above. @lburgazzoli may want to add his/Camel K perspective.

[gsmet]

I'm not entirely sure this would have any consequence on the prod team. It should just be an additional constraint, not something that needs packaging.

But I will let @aloubyansky to comment on this.

[gsmet]

Pinging @zakkak too.

[lburgazzoli]

Note that the js-dsl extension is not supported in CEQ product currently and will hardly be in the future because of the above. @lburgazzoli may want to add his/Camel K perspective.

I don't think that we will have the js-dsl in the produce any time soon so I'm fine with everything that reduces the maintenance

[zakkak]

@gsmet thanks, this makes the life of Camel Quarkus easier in the community, but IIRC, org.graalvm.js:js is not available on Mandrel (cc @zakkak @galderz ).

Correct

If that's really the case this will make the life of the prod team harder.

I am not sure that's true. There are other parts of GraalVM that are not supported in Mandrel as well (and thus not supported in the product), but AFAIK this has not caused any major issues before.

Note that the js-dsl extension is not supported in CEQ product currently and will hardly be in the future because of the above. @lburgazzoli may want to add his/Camel K perspective.

That makes sense.

I'm not entirely sure this would have any consequence on the prod team. It should just be an additional constraint, not something that needs packaging.

But I will let @aloubyansky to comment on this.

+1

[aloubyansky]

AFAICS, it's not a problem for prod.

[quarkus-bot]

Failing Jobs - Building 97b10e5

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
⌛	JVM Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17 MacOS M1
✖	JVM Tests - JDK 18	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/reactive-messaging-hibernate-orm 

📦 integration-tests/reactive-messaging-hibernate-orm

✖ io.quarkus.it.kafka.KafkaConnectorTest.testFruits line 50 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <1> within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

---

⚙️ JVM Tests - JDK 18 #

- Failing: integration-tests/reactive-messaging-hibernate-orm 

📦 integration-tests/reactive-messaging-hibernate-orm

✖ io.quarkus.it.kafka.KafkaConnectorTest.testFruits line 50 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <1> within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

[gsmet]

@ozangunalp I don't know what's happening with this test lately but it has been extremely unstable. Either we fix it quickly or we need to disable it.

[ozangunalp]

@gsmet Thanks for the heads up! I was preparing the fix: #29433