UI.apps build failed Help | Community
Skip to main content
J
JunghwanKi1
May 21, 2024
Solved

UI.apps build failed Help

  • May 21, 2024
  • 4 replies
  • 1054 views

 

why ui.apps build failed ???

 

 

ERROR LOG : 

 

Exception in thread "main" java.lang.StackOverflowError
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)
at org.apache.sling.scripting.sightly.compiler.expression.SideEffectVisitor.evaluate(SideEffectVisitor.java:84)
at org.apache.sling.scripting.sightly.compiler.expression.nodes.BinaryOperation.accept(BinaryOperation.java:109)
at org.apache.sling.scripting.sightly.java.compiler.impl.GenHelper.typeCoercion(GenHelper.java:45)
at org.apache.sling.scripting.sightly.java.compiler.impl.operator.ConcatenateOpGen.generate(ConcatenateOpGen.java:42)
at org.apache.sling.scripting.sightly.java.compiler.impl.ExpressionTranslator.visit(ExpressionTranslator.java:107)

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 aanchal-sikka

@junghwanki1 

 

Please check what version of maven-assembly-plugin are you using:

 

<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>3.3.0</version>

 Please try upgrading it

4 replies

HrishikeshKagne
Community Advisor
HrishikeshKagneCommunity Advisor
Community Advisor
May 21, 2024

Hi @junghwanki1 ,

When building an AEM project, the `ui.apps` module is responsible for packaging the application's user interface components and configurations. If the `ui.apps` build fails, it can be due to a variety of reasons. Here are some common causes and troubleshooting steps:

1. Check the build logs: The build logs can provide valuable information about the cause of the failure. Look for any error messages or stack traces that might indicate the source of the problem.

2. Check the project structure: Make sure that the project structure is correct and that all required files and directories are present. Check that the `ui.apps` module is properly configured and includes all necessary dependencies.

3. Check the Maven settings: Ensure that the Maven settings are correct and that the AEM instance is properly configured. Check that the Maven repository is accessible and that the AEM credentials are correct.

4. Check the code: Review the code in the `ui.apps` module and look for any syntax errors, missing dependencies, or other issues that might cause the build to fail. Check that the code follows best practices and conventions for AEM development.

5. Check the AEM instance: Ensure that the AEM instance is running and that all required services and bundles are active. Check that the AEM instance has enough resources (e.g. memory, CPU) to handle the build process.

6. Clean and rebuild: Try cleaning the project and rebuilding it from scratch. This can help resolve any issues with cached files or dependencies.

7. Update dependencies: Check that all dependencies are up-to-date and compatible with the AEM version being used. Update any outdated dependencies and try rebuilding the project.

8. Seek help: If the issue persists, consider reaching out to the AEM community or Adobe support for further assistance. They may be able to provide more specific guidance based on your AEM version and configuration.

It's important to note that without more context or access to your specific codebase, it's difficult to provide a definitive solution. The steps above are general troubleshooting suggestions to help you identify and resolve the issue.

Hrishikesh Kagane
    TarunKumar
    Community Advisor
    TarunKumarCommunity Advisor
    Community Advisor
    May 21, 2024

    Hi @junghwanki1 ,

    Are you getting this error after any change in any of your custom components. It seems more like an error from sightly/HTL.
    Can you check if you have used any sightly statement which is not compatible.


    Thanks
    Tarun

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity AdvisorAccepted solution
      Community Advisor
      May 21, 2024

      @junghwanki1 

       

      Please check what version of maven-assembly-plugin are you using:

       

      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-assembly-plugin</artifactId>
      <version>3.3.0</version>

       Please try upgrading it

      Aanchal Sikka
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        June 4, 2024

        @junghwanki1 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...