/apps/<project>/install/<core package> not updating | Community
Skip to main content
khamat_bn
khamat_bn
Level 4
May 31, 2020
Solved

/apps/<project>/install/<core package> not updating

  • May 31, 2020
  • 5 replies
  • 8057 views

Hi Folks,

I have install folder in apps/project/install and it has core Jar file. But when I do mvn clean install -PautoInstallPackage then core jar is not updating. It's only working at the first build.

Also when I replicating ui.apps then I can see install folder and bundle in system/console(in active state) but pages is not fetching bundle classes. Getting Below error

org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.scripting.sightly.SightlyException: Compilation errors in org/apache/sling/scripting/sightly/apps/myproj/components/content/categoryButtons/

 

So I have again need to deploy in publish instance via cmd 

mvn -PautoInstallPackage clean install -Daem.port=4503

 

My requirement is - when I am replicating ui.apps then core-bundle also needs to go in publish so that I have not to use next command for publisher specifically.

 

Find my pom.xml(project level) https://github.com/NDSoftwareSolutions/AEM/blob/master/pom.xml

 

    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 BrianKasingli

    @khamat_bn 

    Seems like a strange issue. Before mvn builld, can you follow these actions:

    1. Visit, http://localhost:4502/system/console/bundles, and delete the bundle from here.
    2. Visit, http://localhost:4502/crx/de/index.jsp, and remove the /apps/project/install/*.jar.
    3. Visit, http://localhost:4502/crx/packmgr/index.jsp, and delete the install package from here.
    4. mvn build.

    This is a weird scenario. It shouldn't be behaving like this. I reviewed your pom.xml for ui.apps, and parent pom, and it looks okay. the SNAPSHOT exists; SNAPSHOTS ensures that when new packages are uploaded into AEM, it will allow the content packages + jar files to be overwritten, whereas without the SNAPSHOT label, you are forced to increment the version of the bundle version.

    If this is still not working, I'm suggesting that you try to build your code into a new fresh AEM instance, and test out the installation from there.

    5 replies

    Ankur_Khare
    Community Advisor
    Ankur_KhareCommunity Advisor
    Community Advisor
    May 31, 2020

    Update your pom to use snapshot version.

    Refer this link-

    https://stackoverflow.com/questions/46468457/what-is-the-use-of-snapshot-in-pom-file-aem-cq

      khamat_bn
      khamat_bnAuthor
      Level 4
      May 31, 2020

      Hi @ankur_khare  , Thanks for responding. I have snapshot version present in all pom.xml and i tried by changing the version no. as well then also the changes are not refelecting in my publish env.

       

      <modelVersion>4.0.0</modelVersion>
      <groupId>com.myProj.id</groupId>
      <artifactId>myProj-promo</artifactId>
      <version>1.0.1-SNAPSHOT</version>
      <packaging>pom</packaging>

       

      ArpitVarshney
      Community Advisor
      ArpitVarshneyCommunity Advisor
      Community Advisor
      May 31, 2020

      Hi @khamat_bn 

      Is it possible for you to share a sample of your ui.apps pom.xml? 

       

      Regards,

      Arpit

        khamat_bn
        khamat_bnAuthor
        Level 4
        May 31, 2020
        Hi @arpitvarshney Please find my ui.apps pom.xml here https://github.com/NDSoftwareSolutions/AEM/blob/master/pom.xml%20-%20ui.apps
        VeenaVikraman
        Community Advisor
        VeenaVikramanCommunity Advisor
        Community Advisor
        June 1, 2020

        "when I do mvn clean install -PautoInstallPackage then core jar is not updating" -  Is it like the bundle is not reflecting your latest changes each time ? Just make sure that every-time you install your package to any ENV , there should be a version upgrade else sometimes you might not see your updated changes in the bundle 

         

          U
          Adobe Employee
          user05162Adobe Employee
          Adobe Employee
          June 1, 2020

          Few things to try:

           

          - If you take the jar file and install it directly via /system/console/bundles, does it work?

          - Go to /system/console/osgi-installer and check the status of the jar file after the package is installed

          - Also, check if there are any errors in the log files when package is installed.

            BrianKasingli
            Community Advisor and Adobe Champion
            BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
            Community Advisor and Adobe Champion
            June 1, 2020

            @khamat_bn 

            Seems like a strange issue. Before mvn builld, can you follow these actions:

            1. Visit, http://localhost:4502/system/console/bundles, and delete the bundle from here.
            2. Visit, http://localhost:4502/crx/de/index.jsp, and remove the /apps/project/install/*.jar.
            3. Visit, http://localhost:4502/crx/packmgr/index.jsp, and delete the install package from here.
            4. mvn build.

            This is a weird scenario. It shouldn't be behaving like this. I reviewed your pom.xml for ui.apps, and parent pom, and it looks okay. the SNAPSHOT exists; SNAPSHOTS ensures that when new packages are uploaded into AEM, it will allow the content packages + jar files to be overwritten, whereas without the SNAPSHOT label, you are forced to increment the version of the bundle version.

            If this is still not working, I'm suggesting that you try to build your code into a new fresh AEM instance, and test out the installation from there.

              Terms & ConditionsAccessibility statement

              Loading footer...