6.2 unresolved bundles | Community
Skip to main content
lebom50735824
lebom50735824
Level 2
February 20, 2017

6.2 unresolved bundles

  • February 20, 2017
  • 2 replies
  • 6226 views

Hi,

I've just installed AEM 6.2 in our environment and installed an AEM 6.1 package on it. I using the Uber APIs but the following can't resolve :

com.day.cq.commons,version=[6.0,7) -- Cannot be resolved
com.day.cq.commons.date,version=[5.7,6) -- Cannot be resolved
com.day.cq.commons.inherit,version=[5.7,6) -- Cannot be resolved
com.day.cq.commons.jcr,version=[6.0,7) -- Cannot be resolved
com.day.cq.commons.mail,version=[5.7,6) -- Cannot be resolved

Any idea on how to resolve these?

lebom

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Prince_Shivhare
Community Advisor
Prince_ShivhareCommunity Advisor
Community Advisor
February 20, 2017

Hi ,
 

Please let us know which dependency you added in POM file.

 

~ Prince Shivhare

smacdonald2008
smacdonald2008
Level 10
February 20, 2017

Rebuild your OSGi using Maven 10 Archetype and Urber 6,2 -- see: 

https://helpx.adobe.com/experience-manager/using/first-arch10.html

Notice the use of Urber 6.2 in the POM file. 

smacdonald2008
smacdonald2008
Level 10
February 20, 2017

If you still get that error - use depen finder in AEM and get the correct version in AEM for this package, Make sure you specify that package in your POM. 

But the most important thing is to use the 6.2 Urber version in your POM file for AEM 6.2. 

lebom50735824
lebom50735824Author
Level 2
February 24, 2017

you can also try.

In the parent pom.xml:

<dependency>
                <groupId>com.adobe.aem</groupId>
                <artifactId>uber-jar</artifactId>
                <version>6.2.0-SP1</version>
                <scope>provided</scope>
                <classifier>apis</classifier>
            </dependency>

Core Pom file:
<dependency>
                  <groupId>com.adobe.aem</groupId>
                  <artifactId>uber-jar</artifactId>
                  <classifier>apis</classifier>
            </dependency>

UI Pom file:
<dependency>
                  <groupId>com.adobe.aem</groupId>
                  <artifactId>uber-jar</artifactId>
                  <classifier>apis</classifier>
            </dependency>

 

~ Prince


Hi,

I managed to get the code to build with 

main

<dependency>
                <groupId>com.adobe.aem</groupId>
                <artifactId>uber-jar</artifactId>
                <version>6.2.0-SP1</version>
                <!-- classifier>nonobfuscated-apis</classifier -->
                <scope>provided</scope>
            </dependency>

core

<dependency>
            <groupId>com.adobe.aem</groupId>
            <artifactId>uber-jar</artifactId>
            <version>6.2.0-SP1</version>
            <classifier>apis</classifier>
            <scope>provided</scope>
        </dependency>

ui

no 6.2 dependency

After that I installed our main bundle successfully. Then I installed our main package but after installing the package, the file structure that starts with / doesn't appear. Only the / appears. In our production application this structure is something like :

/

  apps

  bin

  content

  etc

In the log file I see the exception "24.02.2017 10:35:06.517 *ERROR* [10.5.2.97 [1487925306517] GET /crx/packmgr/installstatus.jsp HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl ServletResolver service missing, cannot ser
vice requests , sending status 503"

Is this the reason the application structure is not created after installing main package?

Terms & ConditionsAccessibility statement

Loading footer...