The following api specs are unavailable, please check if there are updates required.

The following api specs are unavailable, please check if there are updates required.

stop test yaml overriding main yaml in jar

account/pom.xml and usage-management/pom.xml registered src/test/resources inside the production block (a typo that the other 17 standalone modules avoid by using ).

Maven copied both directories into target/classes/, with the test application.yaml overwriting the main one — so the produced jar shipped without the api.<module>.basepath: ${general.basepath:/} bridge that standalone deployments rely on.

Result: GENERAL_BASEPATH was effectively ignored since 1.5.0, controllers fell back to the @controller "/" default and routes were mounted at the wrong path (e.g. /billingAccount instead of /tmf-api/accountManagement/v4/billingAccount).

Aligning these two modules with the testResources pattern used everywhere else fixes the regression with no source or behavioural change.

all-in-one is unaffected (its pom never had the typo) and no source changes are needed.

The following api specs are unavailable, please check if there are updates required.