Adriano Machado created CAMEL-23972:
---------------------------------------
Summary: IBM MQ test infra does not handle unsupported Linux ARM64
centrally
Key: CAMEL-23972
URL: https://issues.apache.org/jira/browse/CAMEL-23972
Project: Camel
Issue Type: Bug
Reporter: Adriano Machado
Observed while reviewing changes in components/camel\-jms that add
@DisabledOnOs\(OS.LINUX, architectures = {"aarch64", "aarch\_64"}\) to the two
IBM MQ JMS tests.
Problem
\- The unsupported\-platform knowledge is being added at the test class level
in
components/camel\-jms/src/test/java/org/apache/camel/component/jms/JmsComponentIbmMQTest.java
and
components/camel\-jms/src/test/java/org/apache/camel/component/jms/issues/JmsReplyToIbmMQTest.java.
\- The IBM MQ test infra already carries related metadata in
test\-infra/camel\-test\-infra\-ibmmq/src/main/resources/org/apache/camel/test/infra/ibmmq/services/container.properties
via ibm.mq.container.version.exclude=amd64,arm64,ppc64le,s390x,x86\_64.
\- At runtime, org.apache.camel.test.infra.common.LocalPropertyResolver only
resolves and ., so the version.exclude metadata is not consumed when
org.apache.camel.test.infra.ibmmq.services.IbmMQServiceFactory creates the
local container service.
Impact
\- Unsupported Linux ARM64 handling is duplicated in individual tests instead
of living in the shared IBM MQ infra.
\- Future tests that use IbmMQServiceFactory.createService\(\) can still fail
the same way unless they remember to add their own skip.
\- Runtime behavior and container metadata can drift apart.
Suggested direction
\- Move unsupported\-platform handling into the IBM MQ test infra, or into a
shared test\-infra mechanism used by service factories.
\- Make unsupported platforms skip or short\-circuit before container startup.
\- Remove per\-test annotations once the shared handling exists.
AI\-generated issue drafted by Codex on behalf of ammachado.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
