Level 3

Solved

I am getting errors while building the code taken from wknd git clone

Forum|Forum|1 year ago
November 8, 2024
8 replies
2285 views

I have taken project clone using git clone, project URL (adobe/aem-guides-wknd: Tutorial Code companion for Getting Started Developing with AEM Sites WKND Tutorial). After this have tried to build the project using the below command
mvn clean install -PautoInstallSinglePackage -Pclassic as mentioned in the read me documentation.
but getting below error. Kindly help me on this how to resolve.
I have tried all the possible ways available in the internet regarding the issues similar to this one, but no luck, hence seeking here.

Used versions
Java
openjdk version "11.0.10" 2021-01-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.10+9-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.10+9-LTS, mixed mode)

Maven
Maven home: C:\Apache Maven 3.9.9
Java version: 11.0.10, vendor: Red Hat, Inc., runtime: C:\Users\kk\Downloads\java-11-openjdk-11.0.10-1 3\java-11-openjdk-11.0.10-1
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Node
v20.16.0
npm
10.8.1

AEM 6.5.0
Service pack - 6.5.21.0

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 SureshDhulipudi

Please check Maven settings

and also check settings.xml file to allow access to the Maven repositories

Ensure your settings.xml file is correctly configured and includes the necessary repositories

<settings>
<mirrors>
<mirror>
<id>central</id>
<mirrorOf>central</mirrorOf>
<url>https://repo.maven.apache.org/maven2</url>
</mirror>
</mirrors>
</settings>

== for certificate issue - it is required to update certificate in keystore --

keytool -import -alias mycert -keystore $JAVA_HOME/jre/lib/security/cacerts -file mycert.cer

SureshDhulipudi

Accepted solution

Community Advisor

Please check Maven settings

and also check settings.xml file to allow access to the Maven repositories

Ensure your settings.xml file is correctly configured and includes the necessary repositories

<settings>
<mirrors>
<mirror>
<id>central</id>
<mirrorOf>central</mirrorOf>
<url>https://repo.maven.apache.org/maven2</url>
</mirror>
</mirrors>
</settings>

== for certificate issue - it is required to update certificate in keystore --

keytool -import -alias mycert -keystore $JAVA_HOME/jre/lib/security/cacerts -file mycert.cer

VedhaSriAuthor

Level 3

this is my settings.xml file that I created manually

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

<!-- localRepository

| The path to the local repository maven will use to store artifacts.

| Default: ~/.m2/repository

<localRepository>/path/to/local/repo</localRepository>

-->

<!-- interactiveMode

| This will determine whether maven prompts you when it needs input. If set to false,

| maven will use a sensible default value, perhaps based on some other setting, for

| the parameter in question.

| Default: true

-->

<!-- offline

| Determines whether maven should attempt to connect to the network when executing a build.

| This will have an effect on artifact downloads, artifact deployment, and others.

| Default: false

<offline>false</offline>

-->

<!-- pluginGroups

| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.

| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers

| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.

|-->

<!-- pluginGroup

| Specifies a further group identifier to use for plugin lookup.

<pluginGroup>com.your.plugins</pluginGroup>

-->

</pluginGroups>

<!-- proxies

| This is a list of proxies which can be used on this machine to connect to the network.

| Unless otherwise specified (by system property or command-line switch), the first proxy

| specification in this list marked as active will be used.

|-->

<!-- proxy

| Specification for one proxy, to be used in connecting to the network.

<proxy>

<id>optional</id>

<username>proxyuser</username>

<password>proxypass</password>

<host>proxy.host.net</host>

<nonProxyHosts>local.net|some.host.com</nonProxyHosts>

</proxy>

-->

</proxies>

<!-- servers

| This is a list of authentication profiles, keyed by the server-id used within the system.

| Authentication profiles can be used whenever maven must make a connection to a remote server.

|-->

<!-- server

| Specifies the authentication information to use when connecting to a particular server, identified by

| a unique name within the system (referred to by the 'id' attribute below).

| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are

| used together.

<id>deploymentRepo</id>

<username>repouser</username>

<password>repopwd</password>

</server>

-->

<!-- Another sample, using keys to authenticate.

<id>siteServer</id>

<privateKey>/path/to/private/key</privateKey>

<passphrase>optional; leave empty if not used.</passphrase>

</server>

-->

</servers>

<!-- mirrors

| This is a list of mirrors to be used in downloading artifacts from remote repositories.

| It works like this: a POM may declare a repository to use in resolving certain artifacts.

| However, this repository may have problems with heavy traffic at times, so people have mirrored

| it to several places.

| That repository definition will have a unique id, so we can create a mirror reference for that

| repository, to be used as an alternate download site. The mirror site will be the preferred

| server for that repository.

|-->

<!-- mirror

| Specifies a repository mirror site to use instead of a given repository. The repository that

| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used

| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.

<id>mirrorId</id>

<mirrorOf>repositoryId</mirrorOf>

<name>Human Readable Name for this Mirror.</name>

<url>http://my.repository.com/repo/path</url>

</mirror>

-->

</mirrors>

<!-- profiles

| This is a list of profiles which can be activated in a variety of ways, and which can modify

| the build process. Profiles provided in the settings.xml are intended to provide local machine-

| specific paths and repository locations which allow the build to work in the local environment.

| For example, if you have an integration testing plugin - like cactus - that needs to know where

| your Tomcat instance is installed, you can provide a variable here such that the variable is

| dereferenced during the build process to configure the cactus plugin.

| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles

| section of this document (settings.xml) - will be discussed later. Another way essentially

| relies on the detection of a system property, either matching a particular value for the property,

| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a

| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.

| Finally, the list of active profiles can be specified directly from the command line.

| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact

| repositories, plugin repositories, and free-form properties to be used as configuration

| variables for plugins in the POM.

|-->

<!-- profile

| Specifies a set of introductions to the build process, to be activated using one or more of the

| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>

| or the command line, profiles have to have an ID that is unique.

| An encouraged best practice for profile identification is to use a consistent naming convention

| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.

| This will make it more intuitive to understand what the set of introduced profiles is attempting

| to accomplish, particularly when you only have a list of profile id's for debug.

| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.

</activation>

<name>Repository for JDK 1.4 builds</name>

<url>http://www.myhost.com/maven/jdk14</url>

<layout>default</layout>

<snapshotPolicy>always</snapshotPolicy>

</repository>

</repositories>

</profile>

-->

<!--

| Here is another profile, activated by the system property 'target-env' with a value of 'dev',

| which provides a specific path to the Tomcat instance. To use this, your plugin configuration

| might hypothetically look like:

| ...

| <plugin>

| <groupId>org.myco.myplugins</groupId>

| <artifactId>myplugin</artifactId>

| <configuration>

| <tomcatLocation>${tomcatPath}</tomcatLocation>

| </configuration>

| </plugin>

| ...

| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to

| anything, you could just leave off the <value/> inside the activation-property.

<name>target-env</name>

</property>

</activation>

<tomcatPath>/path/to/tomcat/instance</tomcatPath>

</properties>

</profile>

-->

<id>central</id>

<mirrorOf>central</mirrorOf>

<url>https://repo.maven.apache.org/maven2</url>

</mirror>

</mirrors>

<id>adobe-public</id>

</activation>

<releaseRepository-Id>adobe-public-releases</releaseRepository-Id>

<releaseRepository-Name>Adobe Public Releases</releaseRepository-Name>

<releaseRepository-URL>https://repo.adobe.com/nexus/content/groups/public</releaseRepository-URL>

</properties>

<id>adobe-public-releases</id>

<name>Adobe Public Repository</name>

<url>https://repo.adobe.com/nexus/content/groups/public</url>

<updatePolicy>never</updatePolicy>

</releases>

<enabled>false</enabled>

</snapshots>

</repository>

</repositories>

<id>adobe-public-releases</id>

<name>Adobe Public Repository</name>

<url>https://repo.adobe.com/nexus/content/groups/public</url>

<updatePolicy>never</updatePolicy>

</releases>

<enabled>false</enabled>

</snapshots>

</pluginRepository>

</pluginRepositories>

</profile>

</profiles>

<activeProfile>adobe-public</activeProfile>

</activeProfiles>

</settings>

kapil_rajoria

Community Advisor

Hi @vedhasri tried the same project in my PC and it worked like charm with no errors.

I was using these versions:
java: 11.0.19
maven: 3.9.6
npm: 10.3.0

Try using the same version of java. Sometimes java is responsible.
Also, please share any errors above BUILD FAILURE part in the image you shared.

VedhaSriAuthor

Level 3

Hi @kapil_rajoria , here is the above part of the build process

kapil_rajoria

Community Advisor

I can see no errors. Sometimes this section is also helpful. Please try changing the version of java.

KrassimirBo

Level 3

Hello @vedhasri ,

Find the solution here - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-build-wknd-project-sun-security-provider-certpath/m-p/397329

Krass

gkalyan

Community Advisor and Adobe Champion

@vedhasri The issue in the screenshot is due to cert trust issue. This is quite common.

There is one article on how to resolve this issue by VeenaVikraman

Try to follow the steps in the below article.

https://www.linkedin.com/pulse/sunsecurityvalidatorvalidatorexception-pkix-path-failed-vikraman

If you still face issue, do let us know here and we will try to solve this in a different way.

VedhaSriAuthor

Level 3

Hi @gkalyan , this looks like similar to my issue. But in the above article they have added certificate path in JRE folder inside Java JDK. But now a days java is coming without JRE so how can I achieve this without having JRE inside my Java folder. Also as mentioned in the article, certificate of the URL should saved in .cer format but this is not possible now days chrome or edge browsers not providing to export the certificate in such format. Assist me if you have anything.

PRATHYUSHA_VP

Community Advisor

Adding additional info -

Start command prompt terminal with administrator rights and run the maven command

Find the related issue over here -

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/while-creating-new-project-getting-error-error-merging-velocity/m-p/714299#M176531

Hope this helps

Thanks

VedhaSriAuthor

Level 3

Hi @prathyusha_vp , I am using company laptop so I can't run the command prompt in admin mode.

MukeshYadav_

Community Advisor

Hi @vedhasri ,

Could you please try to add arguments mentioned here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-build-wknd-project-sun-security-provider-certpath/m-p/397329

mvn clean install -PautoInstallPackage -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true

Thanks

VedhaSriAuthor

Level 3

Already tried that commands but not working.

MukeshYadav_

Community Advisor

You may try https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/could-not-find-artifact-org-apache-commons-commons-imaging-jar-1/m-p/559841

Thanks

Manu_Mathew_

Community Advisor

@vedhasri

Ensure your Maven settings file (~/.m2/settings.xml) correctly points to the Adobe repository

<id>adobe-public-releases</id> <url>https://repo.adobe.com/nexus/content/groups/public/</url> (could try HTTP once to check)

It could be because of the firewall via corporate networks, You could update the proxy details-

<proxy>

<id>example-proxy</id>

<host>proxy.example.com</host> <port>8080</port> <username>proxyuser</username>

<password>somepassword</password> <nonProxyHosts>www.google.com|*.example.com</nonProxyHosts>

</proxy>

</proxies>

You can also try an upgrade to a more recent JDK version.

This also could be because the SSL certificate of the Adobe repository is not trusted by your JVM.

kautuk_sahni

Community Manager

@vedhasri Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded