CAMEL-21715: Fix test-jar dependencies

[christophd]

Description

• Since we have been moving some classes in the test-infra-* modules from src/test/java to src/main/java we need to explicitly depend on both test-jar and normal typed dependencies
• Maven will figure it out but IDEs such as IntelliJ raise compile errors
• Explicitly add dependency to test-infra-* modules to avoid compile errors in IntelliJ due to test-jar typed dependencies

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Fixes CAMEL-21715

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[davsclaus]

so we need both test and test-jar dependencies ?

[christophd]

yes, seems only a few classes have been moved from src/test/java to /src/main/java
@Croway maybe knows more

[christophd]

this is only for IDEs like IntelliJ because Maven itself will figure out the transitive dependency when the test-jar is given in the POM as a dependency. IntelliJ complains with compile errors. I think this is because the IDE strictly separates test and main dependency tree

[Croway]

            <groupId>org.apache.camel</groupId>
            <artifactId>camel-test-infra-artemis</artifactId>
            <version>${project.version}</version>
            <scope>test</scope>
            <type>test-jar</type>
        </dependency>

The test jar one is enough since the following plugin https://github.com/apache/camel/blob/main/test-infra/pom.xml#L108 will assembly both test and main classes into the test-jar

[christophd]

@Croway ah was not ware of this. but why is IntelliJ showing those compile errors then? Is the assembly disabled when using the -Dquickly option?

[Croway]

this is only for IDEs like IntelliJ because Maven itself will figure out the transitive dependency when the test-jar is given in the POM as a dependency. IntelliJ complains with compile errors. I think this is because the IDE strictly separates test and main dependency tree

oh, this is strange, actually I didn't notice it in intellij

[Croway]

@Croway ah was not ware of this. but why is IntelliJ showing those compile errors then? I the assembly disabled when using the -Dquickly option?

no, it is not disabled with -Dquickly option

[christophd]

am I the only one seeing the compile errors in the IDE? for instance when opening org.apache.camel.component.amqp.AMQPSAuthRouteTest

[Croway]

This is the only issue I see on the ide