i'm facing this error while building for AEMaaCS | Community
Skip to main content
K
KarthickVe
Level 4
May 2, 2023
Solved

i'm facing this error while building for AEMaaCS

  • May 2, 2023
  • 4 replies
  • 3694 views

[ERROR] The analyser found the following errors for author and publish :
[ERROR] [api-regions-exportsimports] org.xhtmlrenderer:flying-saucer-pdf-itext5:9.1.22: Bundle flying-saucer-pdf-itext5:9.1.22 is importing package(s) [
Package com.itextpdf.text;version=[5.5,6), Package com.itextpdf.text.pdf;version=[5.5,6)] in start level 20 but no visible bundle is exporting these for
that start level in the required version range. (aem:sample:core-aemaacs.all:1.0.0-SNAPSHOT)
[ERROR] [api-regions-exportsimports] aem:sample:core-aemaacs.core:1.0.0-SNAPSHOT: Bundle core-aemaacs.core:1.0.0-SNAPSHOT is importing package(s) [co
m.maxmind.geoip2.model, com.maxmind.geoip2, com.maxmind.db, com.maxmind.geoip2.exception, com.adobe.acs.commons.email, com.maxmind.geoip2.record] in start level 20 but no bundle is exporting these for that start level.

 

Can anyone guid me that how to embed or export this dependency? or a way fix this issue?

i'm using 35v archetype.

 

 

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

This issue resolved after make use of Export-Package in bnd-plugin

Export-Package

 

4 replies

nitesh_kumar-1
Adobe Employee
nitesh_kumar-1Adobe Employee
Adobe Employee
May 2, 2023

Hi @karthickve ,

 

You need to make sure these bundles are embedded in the container (all) project, otherwise during runtime Cloud instance won't have these bundles to refer to. which is why you are seeing this error.

Make sure these bundles are embedded properly in the POM file of the container, you can refer to this article here.

https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html 

 

Hope this helps!

 

Regards,

Nitesh

    Jagadeesh_Prakash
    Community Advisor
    Jagadeesh_PrakashCommunity Advisor
    Community Advisor
    May 2, 2023

    @karthickve  Add below dependencies in all pom.xml file (Version can be any your preffered one)

    <dependency>
        <groupId>com.itextpdf</groupId>
        <artifactId>itextpdf</artifactId>
        <version>5.5.13</version>
    </dependency>

    And also embed the depedency as below  

    <embedded>
        <groupId>com.itextpdf</groupId>
        <artifactId>itextpdf</artifactId>
        <target>/apps/xxxx/install</target>
    </embedded>

    Hope this works !!!!

      K
      KarthickVeAuthor
      Level 4
      May 3, 2023

      Thanks, 

      i have also had this issue

      m.maxmind.geoip2.model, com.maxmind.geoip2, com.maxmind.db, com.maxmind.geoip2.exception, com.adobe.acs.commons.email, com.maxmind.geoip2.record] 

        rawvarun
        Community Advisor
        rawvarunCommunity Advisor
        Community Advisor
        May 2, 2023

        Is this happening on the local AEM cloud sdk jar or AEM as a cloud environment?

          K
          KarthickVeAuthor
          Level 4
          May 8, 2023

           local AEM cloud sdk jar 

            K
            KarthickVeAuthorAccepted solution
            Level 4
            May 8, 2023

            This issue resolved after make use of Export-Package in bnd-plugin

            Export-Package

             

              durga_kavali
              durga_kavali
              Level 3
              July 6, 2023

              @karthickve  am also facing the same issue , could you please let us know how you have added in pom.xml ?

                K
                KarthickVeAuthor
                Level 4
                July 6, 2023

                step 1:Go to core/pom.xml

                step 2: please find the below plugin

                bnd-maven-plugin

                 step 3: Where add the packages as shown below

                Export-Package: 
                  com.maxmind.geoip2;version="2.16.0",\
                  com.itextpdf;version="5.13.2",\

                step 4: Try to build again and it should resolve the problem.

                  Terms & ConditionsAccessibility statement

                  Loading footer...