Hi,
I am creating a new project using below archetype after that when I run mvn clean install I got an error that ui.frontend module test cases field but I have not made any changes to the test cases files.
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=35 \
-D appTitle="Practice SPA React App" \
-D appId="wknd-spa-react" \
-D artifactId="aem-practice-spa.react" \
-D groupId="com.practice.react" \
-D frontendModule="react" \
-D aemVersion="cloud"
does this archetype work?
Views
Replies
Total Likes
Hi,
Could you please post the actual error you are getting? Also are you trying to deploy project on AEM on prim instance or AEM cloud instance?
Views
Replies
Total Likes
Hi,
I am getting below error but i have deleted all test cases if I run the npm run test in ui. the frontend test get passed.
[INFO] --- frontend-maven-plugin:1.12.0:npm (npm install) @ aem-guides-debugcode.ui.frontend ---
[INFO] Running 'npm install' in C:\Naveen\AEM_Project\aem-guides-debugcode\ui.frontend
[INFO] npm WARN @adobe/aem-react-editable-components@1.1.11 requires a peer of @adobe/aem-spa-page-model-manager@~1.4.0 but none is installed. You must install peer dependencies yourself.removed 1 package and audited 2454 packages in 57.786s
[INFO] npm WARN @adobe/aem-react-editable-components@1.1.11 requires a peer of @adobe/aem-spa-page-model-manager@~1.4.0 but none is installed. You must install peer dependencies yourself.
[INFO] npm WARN sass-loader@6.0.7 requires a peer of node-sass@^4.0.0 but none is installed. You must install peer dependencies yourself.
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.3 (node_modules\fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\webpack-dev-server\node_modules\fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[INFO]
[INFO]
[INFO] 232 packages are looking for funding
[INFO] run `npm fund` for details
[INFO]
[INFO] found 163 vulnerabilities (4 low, 108 moderate, 47 high, 4 critical)
[INFO] run `npm audit fix` to fix them, or `npm audit` for details
[INFO]
[INFO] --- frontend-maven-plugin:1.12.0:npm (npm run test) @ aem-guides-debugcode.ui.frontend ---
[INFO] Running 'npm test' in C:\Naveen\AEM_Project\aem-guides-debugcode\ui.frontend
[INFO]
[INFO] > debugcode@0.1.0 test C:\Naveen\AEM_Project\aem-guides-debugcode\ui.frontend
[INFO] > react-scripts test
[INFO]
[INFO] No tests found, exiting with code 1
[INFO] Run with `--passWithNoTests` to exit with code 0
[INFO] No files found in C:\Naveen\AEM_Project\aem-guides-debugcode\ui.frontend.
[INFO] Make sure Jest's configuration does not exclude this directory.
[INFO] To set up Jest, make sure a package.json file exists.
[INFO] Jest Documentation: facebook.github.io/jest/docs/configuration.html
[INFO] Pattern: - 0 matches
[INFO] npm ERR! Test failed. See above for more details.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for debugcode 1.0.0-SNAPSHOT:
[INFO]
[INFO] debugcode .......................................... SUCCESS [ 0.624 s]
[INFO] debugcode - Core ................................... SUCCESS [ 12.923 s]
[INFO] debugcode - UI Frontend ............................ FAILURE [01:36 min]
[INFO] debugcode - Repository Structure Package ........... SKIPPED
[INFO] debugcode - UI apps ................................ SKIPPED
[INFO] debugcode - UI content ............................. SKIPPED
[INFO] debugcode - UI config .............................. SKIPPED
[INFO] debugcode - All .................................... SKIPPED
[INFO] debugcode - Integration Tests ...................... SKIPPED
[INFO] debugcode - Dispatcher ............................. SKIPPED
[INFO] debugcode - Dispatcher ............................. SKIPPED
[INFO] debugcode - UI Tests ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:54 min
[INFO] Finished at: 2024-11-22T11:07:59+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm (npm run test) on project aem-guides-debugcode.ui.frontend: Failed to run task: 'npm test' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :aem-guides-debugcode.ui.frontend
Thanks
Views
Replies
Total Likes
Hi All,
getting this error
aem-guides-debugcode.ui.apps: Could not resolve dependencies for project com.adobe.aem.guides.debugcode:aem-guides-debugcode.ui.apps:content-package:1.0.0-SNAPSHOT: Could not find artifact com.adobe.aem.guides.debugcode:aem-guides-debugcode.ui.frontend:zip:1.0.0-SNAPSHOT in adobe (https://repo.adobe.com/nexus/content/groups/public/)
Thanks
Views
Replies
Total Likes
Views
Likes
Replies