Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

The import com.day.cq.wcm.webservicesupport.ConfigurationManagerFactory cannot be resolved

Avatar

Level 4

Hi,

I am using import statement com.day.cq.wcm.webservicesupport.ConfigurationManagerFactory in my java class. But am getting a compilation error that the import com.day.cq.wcm.webservicesupport.ConfigurationManagerFactory cannot be resolved.

Below is the maven dependency I used.

    <dependency>
            <groupId> com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-webservice-support</artifactId>
            <version>5.8.44</version>
            <scope>provided</scope>
        </dependency>

I have even added cq-wcm-webservice-support-5.5.6.jar file explicitly but no luck.

Could you please let me know the correct maven dependency.

Thanks,

Kishore

1 Accepted Solution

Avatar

Correct answer by
Level 9

The repo.adobe.com is not intended for browsable  thus not seeing the artifact  means it hasn't been requested via maven yet and thus not proxy-stored on repo.adobe.com yet.  If maven cannot retrieve the dependency, then engage with support team by providing the complete mvn -X output. So that they can make artifacts available.

View solution in original post

2 Replies

Avatar

Level 5

I downloaded the jar from below path but ConfigurationManagerFactory is not inside the package after extracting it. It is confusing as based on below url this interface should be available in the jar. Adobe team can confirm on this.

https://repo.adobe.com/nexus/content/repositories/releases/com/day/cq/wcm/cq-wcm-webservice-support/...

https://docs.adobe.com/docs/en/aem/6-1/ref/javadoc/com/day/cq/wcm/webservicesupport/ConfigurationMan...

Avatar

Correct answer by
Level 9

The repo.adobe.com is not intended for browsable  thus not seeing the artifact  means it hasn't been requested via maven yet and thus not proxy-stored on repo.adobe.com yet.  If maven cannot retrieve the dependency, then engage with support team by providing the complete mvn -X output. So that they can make artifacts available.