Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

when i run mvn install

Avatar

Level 3

"C:\Users\Mohammed Skouti\.jdks\openjdk-20.0.1\bin\java.exe" -Dmaven.multiModuleProjectDirectory=D:\WEB_AEM\mysite "-Dmaven.home=D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\plugins\maven\lib\maven3" "-Dclassworlds.conf=D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\plugins\maven\lib\maven3\bin\m2.conf" "-Dmaven.ext.class.path=D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\plugins\maven\lib\maven-event-listener.jar" "-javaagent:D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\lib\idea_rt.jar=64041:D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\bin" -Dfile.encoding=UTF-8 -classpath "D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\plugins\maven\lib\maven3\boot\plexus-classworlds-2.6.0.jar;D:\intellij IDEA\IntelliJ IDEA Community Edition 2022.1.2\plugins\maven\lib\maven3\boot\plexus-classworlds.license" org.codehaus.classworlds.Launcher -Didea.version=2022.1.2 install
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'parent.relativePath' of POM com.adobe.aem.guides:aem-guides-wknd.dispatcher.cloud:3.2.1-SNAPSHOT (D:\WEB_AEM\mysite\dispatcher.cloud\pom.xml) points at com.mysite:mysite instead of com.adobe.aem.guides:aem-guides-wknd, please verify your project structure @ line 7, column 13
[FATAL] Non-resolvable parent POM for com.adobe.aem.guides:aem-guides-wknd.dispatcher.cloud:3.2.1-SNAPSHOT: Could not find artifact com.adobe.aem.guides:aem-guides-wknd:pom:3.2.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 7, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.adobe.aem.guides:aem-guides-wknd.dispatcher.cloud:3.2.1-SNAPSHOT (D:\WEB_AEM\mysite\dispatcher.cloud\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for com.adobe.aem.guides:aem-guides-wknd.dispatcher.cloud:3.2.1-SNAPSHOT: Could not find artifact com.adobe.aem.guides:aem-guides-wknd:pom:3.2.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 7, column 13 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Process finished with exit code 1

1 Accepted Solution

Avatar

Correct answer by
Level 3

@MohammedSkouti,

 

1. Refresh Snapshot Data:

  • If you're aiming to retrieve a snapshot version of the artifact, ensure you refresh your Maven project to obtain the latest snapshot updates.
  • Execute the command mvn clean install -U to prompt Maven to forcefully refresh and retrieve the most recent snapshot information.

2. Validate Repository URL:

  • Ensure your Maven settings accurately point to the designated repository URL hosting the aem-guides-wknd.dispatcher.cloud component.
  • Confirm the repository URL's accessibility and accurate configuration within your project's pom.xml.

 

3. Verify Artifact Presence:

  • Double-check if the specified aem-guides-wknd.dispatcher.cloud artifact, version 3.2.1-SNAPSHOT, indeed exists in the repository you're utilizing. It's plausible that the artifact hasn't been made available or published in the repository yet.

 

4. Snapshot Repository Inclusion:

  • When dealing with a snapshot version of the artifact, verify that your repository setup accommodates snapshot artifacts.
  • Such artifacts are often stored separately from regular release artifacts, necessitating distinct repository configurations.

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 3

@MohammedSkouti,

 

1. Refresh Snapshot Data:

  • If you're aiming to retrieve a snapshot version of the artifact, ensure you refresh your Maven project to obtain the latest snapshot updates.
  • Execute the command mvn clean install -U to prompt Maven to forcefully refresh and retrieve the most recent snapshot information.

2. Validate Repository URL:

  • Ensure your Maven settings accurately point to the designated repository URL hosting the aem-guides-wknd.dispatcher.cloud component.
  • Confirm the repository URL's accessibility and accurate configuration within your project's pom.xml.

 

3. Verify Artifact Presence:

  • Double-check if the specified aem-guides-wknd.dispatcher.cloud artifact, version 3.2.1-SNAPSHOT, indeed exists in the repository you're utilizing. It's plausible that the artifact hasn't been made available or published in the repository yet.

 

4. Snapshot Repository Inclusion:

  • When dealing with a snapshot version of the artifact, verify that your repository setup accommodates snapshot artifacts.
  • Such artifacts are often stored separately from regular release artifacts, necessitating distinct repository configurations.

 

Avatar

Community Advisor

Hello @MohammedSkouti 

 

It must be due to the mismatch of artifactID and groupID between:

  • The parent thats declared in child module. Example
    <parent>
        <groupId>com.abc.aem.platform.cloud</groupId>
        <artifactId>aem-abc-platform-cloud-tools</artifactId>
        <version>1.0.0-SNAPSHOT</version>
        <relativePath>../pom.xml</relativePath>
    </parent>
  • The group & artifact ID in parent pom. Example
 <groupId>com.abc.aem.platform.cloud</groupId>
 <artifactId>aem-abc-platform-cloud-tools</artifactId>

 

 

Please look for above properties in respective pom and make sure that they match


Aanchal Sikka