I am trying to build ignite 2.8 in windows 10, my java version is 1.8, and maven 3.8.5.
I build source code with the command below:
mvn clean install -P all-java,all-scala,licenses -DskipTests -D maven.javadoc.skip=true.
It failed and showed that:
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ignite-jta: Could not resolve dependencies for project org.apache.ignite:ignite-jta:jar:2.8.0: Failed to collect dependencies at org.ow2.jotm:jotm-core:jar:2.2.3 -> org.ow2.carol:carol:jar:3.0.8 -> org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Failed to read artifact descriptor for org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Could not transfer artifact org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018 from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [apache.snapshots (http://repository.apache.org/snapshots, default, snapshots), ow2-snapshot (http://repository.ow2.org/nexus/content/repositories/snapshots, default, snapshots), ow2 (http://maven.ow2.org/maven2, default, releases)] -> [Help 1]
[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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :ignite-jta
I have checked that the jar file of org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018 is no longer maintained in maven central and i cannot find its backup anywhere. I am not sure how to deal with that.
Related
I'm beginner for this in azure devops.
I'm trying to build with maven, but I got the following error that I don't understand :
[ERROR] Failed to execute goal org.codehaus.mojo:cobertura-maven-plugin:2.7:instrument (package-9af52907-6506-4b87-b16a-9883edee41bc) on project gs-spring-boot: Execution package-9af52907-6506-4b87-b16a-9883edee41bc of goal org.codehaus.mojo:cobertura-maven-plugin:2.7:instrument failed: Plugin org.codehaus.mojo:cobertura-maven-plugin:2.7 or one of its dependencies could not be resolved: Could not find artifact com.sun:tools:jar:0 at specified path /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/../lib/tools.jar -> [Help 1]
[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/PluginResolutionException
You are missing tools.jar in your JDK/JRE. Make sure your JDK version on Azure Pipeline. It seems Cobertura doesn't support Java 1.8 and later:
https://github.com/mojohaus/cobertura-maven-plugin/issues/30
https://github.com/mojohaus/cobertura-maven-plugin/issues/21
So, switch to JaCoCo.
There are some mistanken
[ERROR] Failed to execute goal on project vinsuan-road-platform-comm: Could not resolve dependencies for project com.vinsuan.road.paltform:vinsuan-road-platform-comm:jar:1.0-SNAPSHOT: Failed to collect dependencies at com.vinsuan4cloud:vinsuan-common-core:jar:1.0.0: Failed to read artifact descriptor for com.vinsuan4cloud:vinsuan-common-core:jar:1.0.0: Failure to find com.vinsuan4cloud:vinsuan:pom:1.0.0 in http://xxx.xxx.xxx.xxx:9981/repository/sps_group/ was cached in the local repository, resolution will not be reattempted until the update interval of sps_group has elapsed or updates are forced -> [Help 1]
[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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :vinsuan-road-platform-comm`enter code here`
http://xxx.xxx.xxx.xxx:9981 is out company nexus url，So i'am sorry。
then i found some similar problems，their answer are version not match，however，vinsuan-common-core.jar only one version，So i don't know what,i use some operations,such as clean 、compile、install、mvn dependeny:sources,but ide point the mistaken。
The error says Failure to find com.vinsuan4cloud:vinsuan:pom:1.0.0. There should be a pom file beside the jar in the repo in order maven will able to resolve the dependency
If we use the 'LATEST' parameter when generating the project, the command 'mvn clean install' errors out. Should this parameter be used or should the latest version be provided in the command?
mvn archetype:generate "-DarchetypeGroupId=com.sap.cloud.s4hana.archetypes" "-DarchetypeArtifactId=scp-cf-tomee" **"-DarchetypeVersion=LATEST**" "-DgroupId=com.sap.cloud.s4hana.examples" "-DartifactId=my-app" "-Dversion=1.0-SNAPSHOT"
Error is
Error:
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/springframework/spring-framework-bom/5.1.1.RELEASE/spring-framework-bom-5.1.1.RELEASE.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Could not transfer artifact org.springframework:spring-framework-bom:pom:5.1.1.RELEASE from/to central (https://repo.maven.apache.org/maven2): proxy.myproxy.corp # com.sap.cloud.s4hana:sdk-bom:2.7.1-SNAPSHOT, C:\Users\xxxxxxx\.m2\repository\com\sap\cloud\s4hana\sdk-bom\2.7.1-SNAPSHOT\sdk-bom-2.7.1-SNAPSHOT.pom, line 994, column 25
#[ERROR] The build could not read 1 project -> [Help 1]
[ERROR][ERROR] The project com.sap.cloud.s4hana.examples:address-manager1:1.0-SNAPSHOT (C:\my-app\pom.xml) has 1 error
[ERROR] Non-resolvable import POM: Could not transfer artifact org.springframework:spring-framework-bom:pom:5.1.1.RELEASE from/to central (https://repo.maven.apache.org/maven2): proxy.wdf.sap.corp # com.sap.cloud.s4hana:sdk-bom:2.7.1-SNAPSHOT, C:\Users\xxxxxx\.m2\repository\com\sap\cloud\s4hana\sdk-bom\2.7.1-SNAPSHOT\sdk-bom-2.7.1-SNAPSHOT.pom, line 994, column 25: Unknown host proxy.myproxy.corp -> [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
The version 2.7.1-SNAPSHOT in not a released version. It is not available externally (maven-central). So, you cannot download it from maven central. However, 2.6.1 is available. That is why it works.
Please try with RELEASE instead of LATEST or better use released versions directly.
Please also check that settings.xml does not point to an internal snapshot nexus server and delete the local repository in your .m2 directory.
Have you checked your network configuration?
I can see a proxy and unknown host error in the log.
I'm trying to install DSpace 4.1 on Ubuntu 14.04, but I'm getting a constant error while attempting to build the installation package with Maven (using mvn package), which is:
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.dspace:dspace:4.1
(/home/dspace/dspace-4.1-release/dspace/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.dspace:dspace-parent:4.1:
Failure to find org.sonatype.oss:oss-parent:pom:7 in
http://oss.sonatype.org/content/repositories/releases/ was cached in
the local repository, resolution will not be reattempted until the
update interval of sonatype-releases has elapsed or updates are
forced and 'parent.relativePath' points at no local POM #
org.dspace:dspace-parent:4.1, /home/dspace/dspace-4.1-release/pom.xml,
line 20, 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
I've tried defining a proxy for Maven, I've tried having no proxy for Maven. I tried with both DSpace 4.2 and 4.1. Running mvn clean gets the same error.
I checked the sonatype repository and seemingly the release mentioned by the pom.xml doesn't exist (I didn't make any change to the pom.xml file).
Software info:
OS: Ubuntu 14.04 (Trusty Tahr).
DSpace 4.1, binary release (I've tried with 4.2, binary release, too, but still getting the same error).
Apache Maven 3.0.5.
Try to run mvn package in root folder /home/dspace/dspace-4.1-release/ and not in /home/dspace/dspace-4.1-release/dspace
How To resulve this problem
i have update my java version to java6u23 but it will still create problem so what should i do
i dont know much more about maven
[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/MultipleArtifactsNotFoundException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :mediaPlayer
You appear to be missing a dependency for jna-3.2.4
This isn't available on the central maven repo http://repo1.maven.org/maven2/net/java/dev/jna/jna/
But you can find it in the java.net repo http://download.java.net/maven/2/net/java/dev/jna/jna/3.2.4/
Make sure that you have the java.net repo defined to your maven build.
This can be done iether in your pom, or in the settings.xml in your user home/.m2 directory.