I have a maven build with the below structure.
TEST/pom.xml -in root directory
TEST/A/B/pom.xml- child module
maven clean install works fine from command prompt. But, it fails when I run from jenkins with this error.
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Child module /home/jenkins/workspace/TEST/A/B of /home/jenkins/workspace/TEST/pom.xml does not exist #
Please help here as I have failed to resolve this till now.
Related
I am working with shopizer and I try to use https://github.com/shopizer-ecommerce/shopizer-inventory-csv to upload inventory from a csv file.
I edit . and the I run ./mvnw clean install
But I am getting this error
[ERROR] Failed to execute goal on project shopizer-inventory-csv: Could not resolve dependencies for project com.shopizer:shopizer-inventory-csv:jar:2.0.3-SNAPSHOT: The following artifacts could not be resolved: com.shopizer:sm-core-model:jar:2.0.3-SNAPSHOT, com.shopizer:sm-shop:jar:2.0.3-SNAPSHOT: Could not find artifact com.shopizer:sm-core-model:jar:2.0.3-SNAPSHOT -> [Help 1]
strong text
my build fails when i perform a maven clean install:
i have the following error:
Failed to execute goal org.owasp:dependency-check-maven:5.3.2:check (default) on project
[ERROR] bcpg-jdk15on-1.56.jar: CVE-2005-0366
[ERROR] cucumber-jvm-deps-1.0.5.jar\META-INF/maven/com.thoughtworks.xstream/xstream/pom.xml: CVE-2017-7957, CVE-2016-3674
is there a command to not to fail on error ,tahnks
I would set <failOnError> on false in the configuration of the dependency check maven plugin.
I am trying to verify using this parameter (which work for other projects)
mvn -X verify sonar:sonar -Drevision=4.0.10
Maven fails to download dependency because of the argument not resolved
Failed to execute goal on project APP-ear: Could not resolve
dependencies for project com.orginternational:APP-ear:ear:4.0.10:
Failed to collect dependencies at
com.orginternational:APP-was:war:4.0.10: Failed to read artifact
descriptor for com.orginternational:APP-was:war:4.0.10: Could not
transfer artifact com.orginternational:APP:pom:${revision} from/to en
(https://nexus.example.com/repository/maven-central/): Failed to
transfer file
https://nexus.example.com/repository/maven-central/com/orginternational/APP/$%7Brevision%7D/APP-$%7Brevision%7D.pom
with status code 400 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal on project APP-ear: Could not resolve dependencies for
project com.orginternational:APP-ear:ear:4.0.10: Failed to collect
dependencies at com.orginternational:APP-was:war:4.0.10
Any clue how to fix this please?
I have a multi-module Maven project in one root project I just want to add another maven module in the root project which contains many module, so after calling the parent from the pom.xml child I get the following error:
parent pom:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-dep-mgt (default) on project calender: Found Dependency errors.
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:analyze-dep
-mgt (default) on project calender: Found Dependency errors.
analyze-dep-mgt is a mojo which detects whenever there are dependency mismatches during the final resolution of the build. (https://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html)
There is likely to be a problem with your dependencies. Check this documentation for more info on how to structure your poms. (https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html)
I recently had this error when adding a new dependency in which a transitive dependency was causing the same goal fail. Using an older version of the dependency resolved the issue.
I've been facing an issue with Maven SonarQube plugin (v2.6) when Maven version is recent (strictly larger than 3.1).
Here is what I run:
mvn clean verify -Psonar
mvn org.codehaus.mojo:sonar-maven-plugin:2.6:sonar -Psonar
The first invocation makes sure sources are compiled and JaCoCo agent is prepared.
The interesting part comes, when the second command is run:
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project merlin-schema: Error setting Log implementation. Cause: java.lang.reflect.InvocationTargetException: org/slf4j/Marker -> [Help 1]
Any fix to be published?
Replacing default Maven logging implementation is currently not supported. Ticket created: http://jira.sonarsource.com/browse/MSONAR-122