"com.adobe.cq.sightly,version=[2.2,3) -- Cannot be resolved"

Hi,

I am agree with Scott.

please change the uber jar AEM version to 6.3.

Also check with command mvn clean install -PautoInstallPackage

~Prince

it's working now. Thank you smacdonald2008

Also, there are still unresolved issues for

"javax.persistence -- Cannot be resolved

org.apache.commons.beanutils,version=[1.9,2) -- Cannot be resolved

org.hibernate -- Cannot be resolved

org.hibernate.cfg -- Cannot be resolved

org.hibernate.classic -- Cannot be resolved

org.hibernate.dialect -- Cannot be resolved

org.hibernate.dialect.function -- Cannot be resolved

org.hibernate.transform -- Cannot be resolved

"

Can you please suggest any solution for these...

This is a helpful post, I would also suggest that along with

1. adding the uber jar version changes in the root pom:

<dependency>

               <groupId>com.adobe.aem</groupId>

               <artifactId>uber-jar</artifactId>

                <version>6.3.0</version>

                <classifier>obfuscated-apis</classifier>

               <scope>provided</scope>

</dependency>

2. ensuring that you replace the dependencies for the core pom:

<dependency>

            <groupId>com.adobe.aem</groupId>

            <artifactId>aem-api</artifactId>

  </dependency>

with:

  <dependency>

        <groupId>com.adobe.aem</groupId>

       <artifactId>uber-jar</artifactId>

      <classifier>obfuscated-apis</classifier>

</dependency>

3. Execute: mvn clean install -PautoInstallPackage

Thank you!

Above update is not working for me. I have updated the uber-jar version to 6.3 and 6.4 both not worked. Please help me on this error.

Please help me on this issue. smacdonald2008

Hi,

I am facing a similar issue for AEM 6.4 migration from AEM 6.1.I have added the uber-jar dependency yet its not working for me.

Maven Uber Jar dependency:

               <dependency>

              <groupId>com.adobe.aem</groupId>

               <artifactId>uber-jar</artifactId>

               <version>6.4.0</version>

               <classifier>apis</classifier>

               <scope>provided</scope>

               </dependency>

Also it gives me a build error if I try to add obfuscated-apis

    <dependency>

    <groupId>com.adobe.aem</groupId>

    <artifactId>uber-jar</artifactId>

    <version>6.4.0</version>

    <classifier>obfuscated-apis</classifier>

    </dependency>

Can I know what is the solution for this issue.

com.adobe.cq.sightly,version=[2.2,3) -- Cannot be resolved

In AEM 6.4 SP4 (which I have handy right here) the java package "com.adobe.cq.sightly" is exported by the bundle "com.adobe.cq.sightly.cq-wcm-sightly-extension" and the package version is 3.2.0.

This means, that your code is stil compiled against an older package version of this bundle. Most it is still compiling against AEM 6.1 and your update to the uber-jar is not reflected in your build.

Hi Jorg Hoh,

The AEM 6.4 instance which I am using for migration is one on which I have performed in place migration i.e replaced the AEM 6.1 jar with the new AEM 6.4 jar.

I checked for the com.adobe.cq.sightly.cq-wcm-sightly-extension package in system console of my instance and found its version to be 1.5.12. Please find the below screen shot. Also I have added the cq-wcm-sightly-extension dependency in my project pom.xml ,along with the uber-jar dependency.

       <dependency>

       <artifactId>cq-wcm-sightly-extension</artifactId>

       <version>1.5.12</version>

       <groupId>com.adobe.cq.sightly</groupId>

       <scope>provided</scope>

        </dependency>

I am still facing the same issue.

com.adobe.cq.sightly,version=[2.2,3) -- Cannot be resolved

Also the dependency for com.adobe.cq.sightly.cq-wcm-sightly-extension mentioned under /system/console/depfinder also

has the dependency of :

<dependency>

<artifactId>cq-wcm-sightly-extension</artifactId>

<version>1.5.12</version>

<groupId>com.adobe.cq.sightly</groupId>

<scope>provided</scope>

</dependency>

Do I need to add any other dependency apart from this in my pom.xml ?

Your AEM instance shows the right dependencies for AEM 6.4, but your build environment uses different dependencies; obviously the dependencies of the artifact you provided are overwritten by other artifacts (probably the uber.jar)