UberJar Issues for Migration from 6.1 to 6.2

[sonalik77795449]

Hello,

This has been an ongoing issue for us for the UberJar and we tried a few different options with no luck yet - 

Error We get on the bundle - 

com.day.cq.commons.jcr,version=[5.7,6) -- Cannot be resolved
com.day.cq.replication,version=[5.15,6) -- Cannot be resolved
com.day.cq.workflow,version=[0.0,1) -- Cannot be resolved
com.day.cq.workflow.exec,version=[0.0,1) -- Cannot be resolved
com.day.cq.workflow.metadata,version=[0.0,1) -- Cannot be resolved

Added dependencies - 

Tried with following options - 

1) <dependency>
    <groupId>org.apache.geronimo.specs</groupId>
    <artifactId>geronimo-atinject_1.0_spec</artifactId>
    <version>1.0</version>
    <scope>provided</scope>
</dependency>
<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>uber-jar</artifactId>
    <classifier>obfuscated-apis</classifier>
</dependency>

2)

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

3)

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

All these options have left our bundled in an Installed State with unresolved dependencies mentioned above.

Everytime I have deleted the installed package from freshly trying to do a build and recompiling JSPs.

We were suggested by Adobe to add AEM-6.1-SP2 JAR which was added manually onto our environments which left them in the server failures and a lot of environment issues ,although it did resolve the bundle,we could not go with that solution.

We have also tried to add AEM 6.2 UberJar manually through the Felix console with again leaving the bundle with the above mentioned unresolved dependencies

Any help on this would be highly appreciated.Please help provide inputs.

[Tyler_Maynard]

I'd suggest getting back to the state of the bundles installing and showing that dependencies cannot be resolved, and checking those against the depfinder of that particular instance of AEM: /system/console/depfinder

[sonalik77795449]

Hi Tyler,

The bundle is currently in a Installed state with following unresolved dependencies - 

com.day.cq.commons.jcr,version=[5.7,6) -- Cannot be resolved
com.day.cq.replication,version=[5.15,6) -- Cannot be resolved
com.day.cq.workflow,version=[0.0,1) -- Cannot be resolved
com.day.cq.workflow.exec,version=[0.0,1) -- Cannot be resolved
com.day.cq.workflow.metadata,version=[0.0,1) -- Cannot be resolved

These are all related to UberJar,I have however tried to add them separately by checking the references in the depfinder but it somehow still refers to this old version and shows unresolved.

Is there anyway it can refer to the updated version in the pom.xml.

As per my understanding,we should not be required to add these dependencies separately if we have added UberJar dependency.Still gave it a shot.

[Feike_Visser1]

The "depfinder" is basically replaced with the uber-jar. 

Since AEM6.x the individual dependencies are not available via repo.adobe.com

[Feike_Visser1]

Use version "6.2.0-SP1", also you can use <classifier>apis</classifier>.

For the javax.inject you can use:

<!-- needed for javax.Inject -->
	<dependency>
	<groupId>javax.inject</groupId>
	<artifactId>javax.inject</artifactId>
	<version>1</version>
	<scope>provided</scope>
	</dependency>

instead of org.apache.geronimo.specs

[Feike_Visser1]

First of all the uber-jar are *only* meant for building projects. Not to be installed on top of AEM.

[ompandeyy]

Is there any solution for this ? The original question is still unanswered

[smacdonald2008]

WHen you build your project for a new AEM version - make sure you use the corresponding UBER JAR version.

Never install an OSGi built with a past version on an upgraded version. For example - if you had a project built for AEM 6.2 using UBER JAR 6.2 - you need to rebuild the OSGi bundle using UBER 6.3. See

Scott's Digital Community: Creating an Adobe Experience Manager 6.3 Project using Adobe Maven Archet...

that is the solution to get rid of these unresolved dependencies -

com.day.cq.commons.jcr,version=[5.7,6) -- Cannot be resolved

com.day.cq.replication,version=[5.15,6) -- Cannot be resolved

com.day.cq.workflow,version=[0.0,1) -- Cannot be resolved

com.day.cq.workflow.exec,version=[0.0,1) -- Cannot be resolved

com.day.cq.workflow.metadata,version=[0.0,1) -- Cannot be resolved