SPA App deployment with classic profile | Community
Skip to main content
mrobinson-1
Level 3
Sep 4, 2020 1:13 PM UTC
Solved

SPA App deployment with classic profile

I am trying to deploy an SPA to AEM version 6.5.5 using the -Pclassic build profile, but at the end of the build process, I receive the following warning:

 

[WARNING] The requested profile "classic" could not be activated because it does not exist.

Am I missing something in order to include that profile?

Thanks! 

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

4 replies

Andrei_Dantsou
Andrei_DantsouAccepted solution
Level 3
Sep 4, 2020 2:48 PM UTC

@mrobinson-1 ,

The classic profile can be found in the tutorial code repo:
https://github.com/adobe/aem-guides-wknd-spa/blob/React/create-project-start/all/pom.xml
https://github.com/adobe/aem-guides-wknd-spa/blob/React/create-project-start/core/pom.xml

Regards

Translate
    mrobinson-1Author
    Level 3
    Sep 4, 2020 3:07 PM UTC
    Thank you!!
    Translate
    Andrei_Dantsou
    Andrei_Dantsou
    Level 3
    Sep 4, 2020 2:02 PM UTC

    Hello @mrobinson-1,

    The AEM project archetype (https://github.com/adobe/aem-project-archetype) doesn't include the mentioned profile by default. In order to make your profile available for the build, it should be specified in the "profiles" section of your pom.xml. Please see the documentation for more details about profiles definition.

    Regards

    Translate
      mrobinson-1Author
      Level 3
      Sep 4, 2020 2:21 PM UTC

      Understood. Is there anywhere that has the full profile code? In the documentation, it provides some of it, but not all. There is a '...' which I assume contains collapsed code.

       

      An additional Maven profile, named classic has been added to modify the build to target AEM 6.x environments:
        <!-- AEM 6.x Profile to include Core Components-->
    <profile>
        <id>classic</id>
        <activation>
            <activeByDefault>false</activeByDefault>
        </activation>
        <build>
        ...
    </profile>

       

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...