You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carsten Pfeiffer (Jira)" <ji...@apache.org> on 2024/06/27 07:47:00 UTC

[jira] [Created] (MJAVADOC-798) Consider user settings when using invoker

Carsten Pfeiffer created MJAVADOC-798:
-----------------------------------------

             Summary: Consider user settings when using invoker
                 Key: MJAVADOC-798
                 URL: https://issues.apache.org/jira/browse/MJAVADOC-798
             Project: Maven Javadoc Plugin
          Issue Type: Improvement
            Reporter: Carsten Pfeiffer


I get this in some of our builds:
{code}
[INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:3.7.0:javadoc' has not been previously called for the module: 'de.example:myproject:jar:1.0.0-SNAPSHOT'. Trying to invoke it...
[ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file: /tmp/myproject/myproject-submodule/target/invoker/maven-javadoc-plugin1730810899.txt
[WARNING] Creating fake javadoc directory to prevent repeated invocations: /tmp/myproject/myproject/target/site/apidocs
[ERROR] Error fetching link: /tmp/myproject/myproject/target/site/apidocs. Ignored it.
{code}

And looking at the invoker log, I see that some parent pom cannot be found, because my custom {{settings.xml}} that I specified with {{mvn -s mysettings.xml}} was not considered:

{code}
Invoking Maven for the goals: [org.apache.maven.plugins:maven-javadoc-plugin:3.7.0:javadoc] with no properties

M2_HOME=/home/gis/.m2/wrapper/dists/apache-maven-3.6-bin/5al0cn3ksttl2pq1n2rbut6jh8/apache-maven-3.6.3
MAVEN_OPTS=null
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64
JAVA_OPTS=null

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for de.example:myproject-parent:1.0.0-SNAPSHOT: Failure to find de.example.other:someparent:pom:1.9.0-I26 in https://mynexus/content/groups/releases was cached in the local repository, resolution will not be reattempted until the update interval of releases has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ de.example:myproject-parent:1.0.0-SNAPSHOT, /tmp/myproject/pom.xml, line 8, column 10
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
{code}




--
This message was sent by Atlassian Jira
(v8.20.10#820010)