Some downsteam dependency checks do not like javax dependencies.
javax.cache:cache-api was never a part of Java EE and therefore there is no immediate reason for it to be migrated to the new jakarta namespace. Indeed, there is no jakarta replacement jar available as of now. There is some discussion about having one in https://github.com/jsr107/jsr107spec/issues/415 , but so far, it did not result in any actionable plan.
From the CXF point of view, the above seems to be pretty unimportant. javax.cache:cache-api is pulled via org.apache.cxf:cxf-rt-ws-security and org.ehcache:ehcache where it serves as one of several ways to access the ehcache impl. CXF happens not to use the javax.cache API. My quick tests seem to suggest that it is possible to exclude javax.cache:cache-api from ehcache without replacement.
Some downsteam dependency checks do not like javax dependencies.
javax.cache:cache-apiwas never a part of Java EE and therefore there is no immediate reason for it to be migrated to the new jakarta namespace. Indeed, there is no jakarta replacement jar available as of now. There is some discussion about having one in https://github.com/jsr107/jsr107spec/issues/415 , but so far, it did not result in any actionable plan.From the CXF point of view, the above seems to be pretty unimportant.
javax.cache:cache-apiis pulled viaorg.apache.cxf:cxf-rt-ws-securityandorg.ehcache:ehcachewhere it serves as one of several ways to access theehcacheimpl. CXF happens not to use thejavax.cacheAPI. My quick tests seem to suggest that it is possible to excludejavax.cache:cache-apifrom ehcache without replacement.