Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

com.day.cq.search.impl.builder -- Cannot be resolved

Avatar

Level 2

Hello,

I have a problem with some project dependencies like apache commons collections4 or com.day.cq.search.impl.builder.

     
Imported Packagescom.day.cq.search from com.day.cq.cq-search (305)
com.day.cq.search.impl.builder -- Cannot be resolved
com.day.cq.search.result from com.day.cq.cq-search (305)
com.day.cq.wcm.api from com.day.cq.wcm.cq-wcm-api (418)
javax.jcr,version=[2.0,3) from org.apache.sling.jcr.jcr-wrapper (111)
javax.jcr.nodetype,version=[2.0,3) from org.apache.sling.jcr.jcr-wrapper (111)
javax.servlet.http from org.apache.felix.http.servlet-api (40)
org.apache.sling.api.resource,version=[2.2,3) from org.apache.sling.api (66)
org.osgi.framework,version=[1.5,2) from org.apache.felix.framework (0)
org.osgi.service.cm,version=[1.3,2) from org.apache.felix.configadmin (7)
org.osgi.service.component,version=[1.1,2) from org.apache.felix.scr (31)

Especially for collection4, I had to use an older version whereas it worked normally on my coworkers' machines.

Any idea ?

ty 

 

EDIT : It works now without any reason...

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi ty,

what version of AEM are you using?

You can use the dependency finder to see if the class/package is found in AEM and what version is available: http://<host>:<port>/system/console/depfinder

In your maven project, what scope is the package defined as?

Regards,

Opkar

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

Hi ty,

what version of AEM are you using?

You can use the dependency finder to see if the class/package is found in AEM and what version is available: http://<host>:<port>/system/console/depfinder

In your maven project, what scope is the package defined as?

Regards,

Opkar

Avatar

Level 2

You were on the right way : the scope for this dependency in my pom was provided.

When not using a scope, then no more problem.

Thank You Opkar ;)