Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

com.adobe.icc.ddg.api,version=[3.1,4) -- Cannot be resolved

Avatar

Avatar
Validate 1
Level 2
PriyankP
Level 2

Like

1 like

Total Posts

28 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
PriyankP
Level 2

Like

1 like

Total Posts

28 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
PriyankP
Level 2

26-04-2017

Hello Experts, 

I am trying to use the LetterRenderService to generate Letters(PDFs) on AEM Forms 6.2 OSGi. 

I am using the following Maven dependency on my project. 

<dependency> <groupId>com.adobe.aemfd</groupId> <artifactId>aemfd-client-sdk</artifactId> <version>6.2.0</version> </dependency>

The code compiles fine, but when I deploy the package on my local instance, the bundles shows that it is unable to resolve the package com.adobe.icc.ddg.api,version=[3.1,4) -- Cannot be resolved

I checked depfinder and it shows the Maven dependency as below (please also see the screenshot). 

<dependency>

<groupId>com.adobe.livecycle.icc</groupId> <artifactId>acm-osgi</artifactId> <version>7.1.10</version> <scope>provided</scope> </dependency>

 

I checked Adobe Public Repo and I can't seem to find this dependency there and so if I add this to my project POM file, it throws error, stating that it is unable to find the jar. 

 

How do I go about resolving this issue?

 

Thanks, 

Priyank P

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Ignite 5
Employee
workflowuser
Employee

Likes

135 likes

Total Posts

444 posts

Correct Reply

70 solutions
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Ignite 5
Employee
workflowuser
Employee

Likes

135 likes

Total Posts

444 posts

Correct Reply

70 solutions
Top badges earned
Ignite 5
Ignite 3
Ignite 1
Give Back 50
Give Back 5
View profile
workflowuser
Employee

26-04-2017

This is a known issue in 6.2, has been fixed in 6.3. as workaround in 6.2 do the following to your import package version numbers

                                        

<plugin>

        <groupId>org.apache.felix</groupId>

        <artifactId>maven-bundle-plugin</artifactId>

     <extensions>true</extensions>

     <configuration>

                 <instructions>

                       ...

                       <Import-Package>

                              *; version="[0.0.0, 10.0.0)";

                       </Import-Package>

                 </instructions>

     </configuration>

</plugin>

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
Level 2
PriyankP
Level 2

Like

1 like

Total Posts

28 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
PriyankP
Level 2

Like

1 like

Total Posts

28 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
PriyankP
Level 2

26-04-2017

Thanks. It worked !