Fresh setup a local AEM development environment not working: No marketplace entries found to handle maven-clean-plugin:3.0.0:clean and "] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce" in eclipse | Community
Skip to main content
A
Anonymous
November 26, 2020
Solved

Fresh setup a local AEM development environment not working: No marketplace entries found to handle maven-clean-plugin:3.0.0:clean and "] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce" in eclipse

  • November 26, 2020
  • 2 replies
  • 8171 views

I have followed this guide to the letter on a clean windows pc: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html#set-up-a-local-aem-development-environment 

So have a running author jar, mvn and java installed, eclipse EE setup with the sling and aem "dev tools"

The final step of the instructions is to import the "completed wknd" tutorial. However, the wknd tutorial requires the dev env setup, and dev env setup requires the tutorial.

As a way out of this, I downloaded the source zip from https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-0.0.6

Then I did "file->import->existing maven projects" on the source dir.

But it wont import.

It pops up the error "No marketplace entries found to handle maven-clean-plugin:3.0.0:clean in Eclipse.  Please see Help for more information"

The instructions are also missing two critical steps: 

  1. when you do a fresh install of eclipse, you have to add a jdk under window->preferences->installed JREs
  2. When you create a new run configuration, you have to go to the JRE tab and change it from the default "alternate JRE" to "workspace default jdk".

When I try to run the "install WKND pacakge" configuraiton, I get 3 errors:

 

  1. The requested profile "autoinstallPackage" could not be activated because it does not exist.
  2. No marketplace entries found to handle maven-clean-plugin:3.0.0:clean
  3. Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce (enforce-checksum-of-immutable-files) on project aem-guides-wknd.dispatcher.cloud: Some Enforcer rules have failed.

Here is an example output with the errors:

 

 

[WARNING] Rule 9: org.apache.maven.plugins.enforcer.RequireFileChecksum failed with message: There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/renders/default_renders.any [WARNING] Rule 10: org.apache.maven.plugins.enforcer.RequireFileChecksum failed with message: There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/virtualhosts/default_virtualhosts.any [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for WKND Sites Project - Reactor Project 0.0.6: [INFO] [INFO] WKND Sites Project - Reactor Project ............... SUCCESS [ 0.274 s] [INFO] WKND Sites Project - Core .......................... SUCCESS [ 37.125 s] [INFO] WKND Sites Project - UI Frontend ................... SUCCESS [02:27 min] [INFO] WKND Sites Project - UI apps structure ............. SUCCESS [ 1.010 s] [INFO] WKND Sites Project - UI apps ....................... SUCCESS [ 6.714 s] [INFO] WKND Sites Project - UI content .................... SUCCESS [ 4.449 s] [INFO] WKND Sites Project - UI config ..................... SUCCESS [ 0.254 s] [INFO] WKND Sites Project - UI sample content ............. SUCCESS [ 7.927 s] [INFO] WKND Sites Project - All ........................... SUCCESS [ 3.501 s] [INFO] WKND Sites Project - Integration Tests ............. SUCCESS [05:31 min] [INFO] WKND Sites Project - Dispatcher .................... FAILURE [ 0.109 s] [INFO] WKND Sites Project - UI Tests ...................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 09:02 min [INFO] Finished at: 2020-11-26T17:54:40+01:00 [INFO] ------------------------------------------------------------------------ [WARNING] The requested profile "autoinstallPackage" could not be activated because it does not exist. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce (enforce-checksum-of-immutable-files) on project aem-guides-wknd.dispatcher.cloud: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]

 

 

i notice it says "displatcher.cloud".  Why cloud? I am running a local install, nothing to do with cloud?

 

 

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

You can just go to parent pom.xml, and comment out the "dispatcher.cloud" module. Next, mvn clean install again. Since you do not have the correct profile, head into ui.apps/target/.*.zip, and upload it manually into AEM using the package manager. Your build logs looks fine, except for the dispatcher.cloud maven module.

2 replies

BrianKasingli
BrianKasingliAccepted solution
New Participant
November 26, 2020

You can just go to parent pom.xml, and comment out the "dispatcher.cloud" module. Next, mvn clean install again. Since you do not have the correct profile, head into ui.apps/target/.*.zip, and upload it manually into AEM using the package manager. Your build logs looks fine, except for the dispatcher.cloud maven module.

    Anudeep_Garnepudi
    Anudeep_Garnepudi
    New Participant
    November 26, 2020

    Hi @17382934 

    Import the main folder(aem-guides-wknd-aem-guides-wknd-0.0.6) which has parent pom.xml. 

    Update your Compiler plugin as below

    <!-- Maven Compiler Plugin -->
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
            <source>1.8</source>
            <target>1.8</target>
            <verbose>true</verbose>
        </configuration>
    </plugin>

      A
      Anonymous
      November 26, 2020
      Thanks for the reply. I already imported this directory and eclipse picks up all the pom files, and this is what gives that missing clean error. Which file shall I edit to set the compiler??
      Terms & ConditionsAccessibility statement

      Loading footer...