fix(tests): the Camel ITs follow their move to the api package

[delchev]

Why

The 14.27.0 release run (31936061338) failed in both release-artifacts and release-docker-images at the same place — codbex-atlas-integration-tests did not compile:

DirigibleCommonTestSuiteIT.java:[28,9] cannot find symbol
  symbol: class CamelDirigibleJavaScriptComponentCronRouteIT
... 6 classes

Dirigible PR eclipse-dirigible#6735 ("the camel route ITs publish over HTTP, not through Chrome") converted six Camel route ITs from Selenide/Chrome tests to HTTP-level PredefinedProjectITs and moved them:

Class	14.24.0	14.27.0
CamelDirigibleJavaScriptComponent{Cron,Http}RouteIT	…ui.tests.camel	…api.camel
CamelDirigibleTwoStepsJSInvoker{Cron,Http}RouteIT	…ui.tests.camel	…api.camel
CamelExtractTransformLoad{Jdbc,Typescript}IT	…ui.tests.camel	…api.camel
Camel{Cron,Http}RouteStarterTemplateIT	…ui.tests.camel	…ui.tests.camel (unchanged)

DirigibleCommonTestSuiteIT imported only ui.tests.camel.*, which is exactly why the two starter-template ITs still resolved and the other six did not.

What

Import …api.camel.* alongside the existing …ui.tests.camel.*. Both are needed — the two starter-template ITs stayed put. The @SelectClasses list is unchanged; the same eight ITs run as before.

Also recorded the trap in CLAUDE.md's bump notes: this suite names Dirigible's ITs by reference, so any upstream IT rename/move/removal breaks it, and only at compile time.

Rest of the 14.24.0 → 14.27.0 delta

Checked the other surfaces that drift on a bump; all clean, no changes needed:

• The other 18 ITs the suite references (SecurityIT, CmsSuiteIT, MonitoringShellIT, IntentBuilderShellIT, …) — all still at their declared packages in v14.27.0.
• The forked UI modules (components/ui/menu-help, components/ui/view-welcome) — upstream made no changes to either between v14.24.0 and v14.27.0, so no fork resync.
• application/pom.xml — all 24 dirigible-* artifacts it names still exist in v14.27.0.
• Atlas's own tests — UserInterfaceIntegrationTest, HtmlElementType, IDE.openHomePage()/openIde() all still present; the Home tagline HomePageIT asserts is unchanged in resources-home/index.html.

Verification

mvn clean install -P quick-build + a forced clean test-compile of integration-tests against the real 14.27.0 artifacts: BUILD SUCCESS.

javap on the compiled suite confirms the wildcard resolved as intended — six from api/camel, two still from ui/tests/camel:

integration/tests/api/camel/CamelDirigibleJavaScriptComponentCronRouteIT
integration/tests/api/camel/CamelDirigibleJavaScriptComponentHttpRouteIT
integration/tests/api/camel/CamelDirigibleTwoStepsJSInvokerCronRouteIT
integration/tests/api/camel/CamelDirigibleTwoStepsJSInvokerHttpRouteIT
integration/tests/api/camel/CamelExtractTransformLoadJdbcIT
integration/tests/api/camel/CamelExtractTransformLoadTypescriptIT
integration/tests/ui/tests/camel/CamelCronRouteStarterTemplateIT
integration/tests/ui/tests/camel/CamelHttpRouteStarterTemplateIT

formatter:validate passes.

🤖 Generated with Claude Code