Jenkins build failed, artifactory issue - spring-boot

I am running a Jenkins build and its failing with the below error:
[ERROR] Plugin org.springframework.boot:spring-boot-maven-plugin:2.2.4.RELEASE or one of its
dependencies could not be resolved: Failed to read artifact descriptor for
org.springframework.boot:spring-boot-maven-plugin:jar:2.2.4.RELEASE: Failure to find
org.springframework.boot:spring-boot-maven-plugin:pom:2.2.4.RELEASE in
https://artifactory.abccompany.com:443/artifactory/java was cached in the local repository,
resolution will not be reattempted until the update interval of central has elapsed or updates are forced
I have checked the socket Timeout for repository in the advanced tab, I changed it to 60 secs but still build is failing.
What could be the issue and how to have it resolved?
Any help would be greatly appreciated.
Thank you

You are probably missing some dependencies.
Locate the dependencies you're missing with mvn dependency:tree, then install them manually, and build your project offline once.

Related

Failure to find external:authapi:jar:2005-08-12

Compile openam checked out from svn, and get an error:
Failed to execute goal on project openam-auth-securid: Could not resolve dependencies for project org.forgerock.openam:openam-auth-securid:jar:13.0.0-SNAPSHOT: Failure to find external:authapi:jar:2005-08-12 in http://maven.forgerock.org/repo/releases was cached in the local repository, resolution will not be reattempted until the update interval of forgerock-staging-repo has elapsed or updates are forced -> [Help 1]
Is it a network problem? Did someone meet it before?
The authapi library has been removed from the Maven repository, as there were redistribution issues. In order to build older OpenAM releases you will need to download older OpenAM releases and install the authapi library manually to your local Maven repository.

Jenkins could not resolve dependencies

I have a problem with jenkins version 1.500. i am trying to build a project with a dependency to another project of mine.
The error is:
[ERROR] Failed to execute goal on project projectname: Could not resolve dependencies for project projectname:jar:1.0.0: Failure to find reference-project:jar:1.0.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
If I build this project via console and Maven, the whole projects build succeed.
I checked the dependency jar file in the repository, it is there at the right place.
Does Maven have a own repository or did I miss something?
But under the Jenkins system settings, I chose "Default(~/.m2/repository)" and I did not check the checkbox "use own repository" at the project settings. Any ideas?
UPDATE
I created a extra job for the dependency in jenkins and called the Maven goal install and then everything works fine. Before this step I installed the dependency via Console and mvn install.
Why is there a difference? (i tried the given solution with delete and reinstall, but this did not help)
Simple solution delete the folder from the ~/.m2/repository which represents the artifact you've written about. ~/.m2/repository/${groupId}/... and rebuild. That happens sometimes if you have some problems during download of the artifact etc.
I too have similar problem and tried deleting the folder in ~/.m2/repository/
still its now downloading dependencies from remote repository location to local

Update interval of Maven Central Repo

Having zero experience with Maven, I am running a mvn clean install on a project and this is the error I get:
[ERROR] Failed to execute goal on project dnasequencing.CompaNY.com: Could not resolve dependencies for project com.CompaNY.dnasequencing:dnasequencing.
CompaNY.com:war:1.0-SNAPSHOT: The following artifacts could not be resolved: dsr-kepler:dsr-kepler:jar:0.0.1-SNAPSHOT, dsr-parser:dsr-parser:jar:0.0.1-
SNAPSHOT: Failure to find dsr-kepler:dsr-kepler:jar:0.0.1-SNAPSHOT in http://repo1.maven.org/maven2/ was cached in the local repository, resolution
will not be reattempted until the update interval of Maven_Central_Repo has elapsed or updates are forced -> [Help 1]
Based on these error messages, what is an startingpoint I should take a look for finding what is going wrong?
You can force Maven to update snapshots with the -U flag.
As far as what is going wrong, you can always check out the actual Maven website with your browser and see if the dependency actually exists.
http://search.maven.org/
If the dependency is not hosted in Maven central, then it seems it is a local dependency that you have to install in your local cache (run mvn clean install from that project).

Archiva/Maven failed to execute goal

When I try to build using Archiva/Maven, the system return this message:
Failed to execute goal on project ... The following artifacts could not be resolved: net.sf.josql:josql:jar:1.5, net.sf.josql:gentlyweb-utils:jar:1.5: Failure to find net.sf.josql:josql:jar:1.5 in ... repository/internal was cached in the local repository, resolution will not be reattempted until the update interval of ... has elapsed or updates are forced -> [Help 1]
How can I fix this?
Remove from your local repository directory (or all file with version 1.5):
$M2_HOME/repository/net/fs/josql/josql
It only work when I change from Archiva to Maven (local). Need further investigation...

Could not transfer artifact maven-compiler-plugin from central

I have just downloaded Eclipse Indigo and the m2e plugin, and this error shows up in the pom.xml of my project :
ArtifactResolutionException:
Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom:2.3.2
from http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has elapsed or updates are forced.
Original error: Could not transfer artifact org.apache.maven.plugins:
maven-compiler-plugin:pom:2.3.2 from/to central (http://repo1.maven.org/maven2):
null to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom
I find the original error message to be weird with the null.
I checked that last url and there is indeed a pom file there.
I have tried specifying a mirror in my settings.xml but it doesn't seem to look there anyway, apparently.
Also, when I type mvn clean I get a BUILD SUCCESSFUL message. How come ?
Thank you for helping me out.
Failure to get the POM for a dependency is not considered an error. It is just a warning. This explains why mvn clean is successful. As far as your settings not being consulted have you ensured that you have configured M2E to use your settings file?

Resources