Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Deploying my Code to AEM 6.2 from AEM 6.0

Avatar

Level 2

Currently i am using AEM 6.0 and the build and deployments are doing fine. But when i am deploying the taglib and Services jar to AEM 6.2 the bundles are not starting. My Project is not based on Archtype 10 and i am using an older structure. i have not made any changes in dependencies till now. I am deploying it as it is.

In taglib i am getting the following error. i dont even have commons in the services POM. Can you please advice on the fixes in the POM. When i looked at archetype 10 i did not even find the com.day.cq.commons in the POM. Any ideas on the fix

osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.commons)(version>=5.6.0)(!(version>=6.0.0))) Unresolved requirements: [[com.xxx.www.xxx-www-taglib [472](R 472.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.commons)(version>=5.6.0)(!(version>=6.0.0)))]

In Services i am getting the following error

osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.commons)(version>=5.7.0)(!(version>=6.0.0))) Unresolved requirements: [[com.xxx.www.xxx-www-services [471](R 471.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.commons)(version>=5.7.0)(!(version>=6.0.0)))]

The dependency in Taglib

<!--  CQ BASE LIBRARIES -->
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-core</artifactId>
            <version>5.6.14</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-foundation</artifactId>
            <version>5.6.4</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-api</artifactId>
            <version>5.6.6</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.day.cq</groupId>
            <artifactId>cq-commons</artifactId>
            <version>5.6.4</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-commons</artifactId>
            <version>5.6.4</version>
            <scope>provided</scope>
        </dependency>

----------------------------------------------------------------------------

The dependencies in Services are below, 

<dependency>
            <groupId>com.squeakysand.osgi</groupId>
            <artifactId>squeakysand-osgi</artifactId>
            <scope>compile</scope>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>org.osgi.core</artifactId>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>org.osgi.compendium</artifactId>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.fragment.xml</artifactId>
            <scope>provided</scope>
        </dependency>

        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <scope>provided</scope>
        </dependency>

        <!-- JAVA Servlet -->
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
            <scope>provided</scope>
        </dependency>

        <!-- CQ email service -->

        <dependency>
            <groupId>com.day.cq</groupId>
            <artifactId>cq-mailer</artifactId>
            <version>5.6.4</version>
            <scope>provided</scope>
        </dependency>

         <dependency>
            <groupId>org.apache.commons</groupId>
            <artifactId>commons-email</artifactId>
            <version>1.2</version>
             <scope>provided</scope>
        </dependency>

1 Accepted Solution

Avatar

Correct answer by
Employee

I would start with putting the uberjar as the first dependency, then removing the others one by one.

View solution in original post

3 Replies

Avatar

Level 2

Can i remove all the other dependencies

Avatar

Correct answer by
Employee

I would start with putting the uberjar as the first dependency, then removing the others one by one.