Closed kdesineedi closed 2 years ago
Hi @kdesineedi is this for following the tutorial or just installing the site?
I think you will need to downgrade Core Components below 2.18.0, like https://github.com/adobe/aem-core-wcm-components/releases/tag/core.wcm.components.reactor-2.17.14.
So if following the tutorial, using https://github.com/adobe/aem-project-archetype/releases/tag/aem-project-archetype-35 should work. Release https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-1.1.0 should also work I think...
No luck @godanny86
I think I need to change my mvn version Maven 3.3.9 but the current project I am on uses that version so can you please confirm is there a specific mvn version I need to use ?
I still see the same 4 errors when I used the above package you linked:
INFO] --- maven-install-plugin:2.5.2:install (default-install) @ aem-guides-wknd --- [WARNING] Error injecting: org.apache.maven.artifact.installer.DefaultArtifactInstaller com.google.inject.ProvisionException: Unable to provision, see the following errors:
1) Error injecting: private org.eclipse.aether.spi.log.Logger org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
2) Error injecting: private org.eclipse.aether.spi.log.Logger org.apache.maven.repository.internal.DefaultVersionResolver.logger while locating org.apache.maven.repository.internal.DefaultVersionResolver while locating java.lang.Object annotated with at org.eclipse.sisu.wire.LocatorWiring 3) Error injecting: private org.eclipse.aether.spi.log.Logger org.apache.maven.repository.internal.DefaultVersionResolver.logger while locating org.apache.maven.repository.internal.DefaultVersionResolver while locating java.lang.Object annotated with
4) Error injecting: private org.eclipse.aether.spi.log.Logger org.apache.maven.repository.internal.DefaultVersionResolver.logger [ERROR] while locating org.apache.maven.repository.internal.DefaultVersionResolver [ERROR] while locating java.lang.Object annotated with * [ERROR] at org.eclipse.sisu.wire.LocatorWiring
Upgraded mvn version to Apache Maven 3.6.0 to resolve. Should the required version of mvn be upgraded to this version for the new archetype ?
Also the build succeeded with the following warning:
The requested profile "classic" could not be activated because it does not exist.
when executed with
mvn clean install -PautoInstallSinglePackage -Pclassic
Hi @kdesineedi, glad you got it working!
classic
profile is just something added to the wknd project so that we can have a single code base that is backwards compatible with 6.5 builds. If you generated your project using the Archetype it will not be included or needed.Thanks @godanny86
I am getting build errors while building the wknd project while on Java 8 and Maven 3.3.9.I am on AEM 6.5.9.0 Could you please suggest the appropriate version to use for WKND tutorial for this config as I cannot upgrade any of my versions as my project is on that stack.