AEM Trouble Shootings during package installing
– Web Development
Dependency debugging
When sometimes Intelli J complains about your sytanx
Either re-load your JDK through the project structure or try re-open page.
Or be more specific on folders such as including only one aem project.
Make sure that you have an AEM instance learning.
mvn clean install -PautoInstallSinglePackage -Pclassic -Denforcer.skip=true
ui.frontend complains that it’s failing to run node commands
-
Make sure that you did install the node
-
Make sure that your node version complies with pom.xml
-
Make sure that your NPM and Node version matches to your device version.
Package installation fails due to an enforcer.
If you are on 6.5 on the window, use this command. Apparently this issue happens to people who uses AEM 6.5 on window 10 and 11.
https://github.com/adobe/aem-guides-wknd/issues/201
https://github.com/adobe/aem-guides-wknd/issues/179
mvn clean install -PautoInstallSinglePackage -Pclassic -Denforcer.skip=true
Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin
I really am not sure how other devs have no problem about the versions of jackrabbit but 1.0.3 always throw issues to me. After changing to 1.0.4, the problem disappears.
Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:1.0.2:install (install-package)
This means that your instance is somehow no longer running. Either close your current instance and rerun or double-check if it’s running now.
The instance running command is here:
java -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -jar aem-author-p4502.jar -gui
maven compiler continued failing to achieve the goal
At first, I thought it was a versioning conflict between the POM.XML setup (they normally use Java 8) and my device JDK, which is Java 11.
It turns out some codes had class linking issues under them.test folder.
So I opted it.test module and also commented the it.test-related dependency under it.lanuch folder.
After doing so, finally, all compiling along with packages was done successfully.
Additionally,
<java.version>11</java.version>
<maven.compiler.source>${java.version}</maven.compiler.source>
<maven.compiler.target>${java.version}</maven.compiler.target>
inside of the properties.
Additionally, I changed the versionings like this.
<requireJavaVersion>
<message>Project must be compiled
with Java 8 or higher</message>
<version>${java.version}</version>
</requireJavaVersion>
<!-- Maven Compiler Plugin -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<release>${java.version}</release>
<source>${java.version}</source>
<target>${java.version}</target>
</configuration>
<dependencies>
<dependency>
<!-- update compiler plugin dependency on
ASM for
Java 11 compatibility -->
<groupId>org.ow2.asm</groupId>
<artifactId>asm</artifactId>
<version>6.2</version>
</dependency>
</dependencies>
</plugin>