Replies

Highlighted

Avatar

Avatar

Prince_Shivhare

Avatar

Prince_Shivhare

Prince_Shivhare

22-02-2017

Hey,

I tried it at my end and I was getting the build success.

I haven't added the jar file manually. also I was checking the resolution in Github and got this:

https://github.com/Adobe-Consulting-Services/lazybones-aem-templates/issues/8

 

~ Prince

Highlighted

Avatar

Avatar

lebom50735824

Avatar

lebom50735824

lebom50735824

24-02-2017

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?