We Keep Coding

Maven Error - Failure to find artifact in https://repo.maven.apache.org/maven2 was cached in the local repository

I don't understand following error I am getting while executing : mvn install
I have the javax.transaction:jta:jar:1.0.1B artifact in my m2 repository and I did make sure that the maven is looking at the right repository (By running mvn -X)
Has anybody ever experienced and resolved this kind of error.
Failure to find javax.transaction:jta:jar:1.0.1B in https://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

I had this same problem. The jar was installed in my local .m2 directory.
I had the pom.xml updated with the dependency element for the jar file.
I even added the localRepository element in a local settings.xml (even though this is the default and shouldn't be needed).
The authorities on the directories was what is required:
drwxr-xr-x on directories and -rw-r--r-- on the files in the respository
none of the other items in the list from the DependencyResolutionException were helpful
I decided to try running with sudo on the mvn install and this made the difference (I am on a mac if that matters):
sudo mvn install:install-file -DgroupId=com.nav.abc - DartifactId=xy.abc -Dversion=1.0.0 -Dpackaging=jar - Dfile=abcAdapter/xy.abc.jar
And now it seems to be working!
I don't see any difference in the access authorities on the directories so I'm not sure how this made any difference... but it does work

Since you say the jar is in your local .m2, it is strange that Maven still goes to the central repo to find it, ideally it should not. I am thinking it might be related to a different dependency, for example like in this thread. Could you check if yours if the same scenario?
The other thing you could do is look for a repository where this version of JTA exists and add that repository to your settings.xml or pom.xml, however you have that configured.
One another option is you could try with a different version of JTA jar and see if you run in to the same issue.

Go to the folder contains javax.transaction:jta:jar:1.0.1B in your .m2 and then delete this file _remote.repositories

How can I point to the correct location to the parent pom?

I had to re-install Eclipse, and my previously-working project refuses to compile due to Maven POM error.
The error is
Project build error: Non-resolvable parent POM: Failure to transfer my:my-parent:pom:3.0 from 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.
Original error: Could not transfer artifact my:my-parent:pom:3.0 from/to central (http://repo.maven.apache.org/
maven2): connect timed out and 'parent.relativePath' points at wrong local POM
I know the SVN location for the parent POM on the company Intranet, but not sure where it should be configured in Eclipse/Maven so parent POM is read from there instead of from Apache Maven repo

You must configure current maven repositories in your .m2 directory in settings.xml file.
And if you want to force to check for artifacts in remote repositories you must do a mvn compile with -U option to force an update

Since you are in company network may be a proxy issue. Check the settings.xml and check the required proxy is setup properly
Try force maven update
mvn clean install -U

As per NullPointerException's comment, the problem was that my previous Eclipse install had a custom .m2 location ( preferences -> maven -> User Settings ) and new install was pointing to incorrect .m2.
Changing that to correct location fixed the issue

Cannot find disco.jar dependency for Maven Project

I've just started helping my professor out for his research project and I'm trying to get it set up on my local windows computer. I'm stuck with this error:
Failed to execute goal on project tornado: Could not resolve
dependencies for project tornado:tornado:jar:0.0.1-SNAPSHOT: Failure
to find com.disco:disco:jar:10.2.0 in http://clojars.org/repo was
cached in the local repository, resolution will not be reattempted
until the update interval of clojars.org has elapsed or updates are
forced
Notes:
It's a maven project being run on eclipse.
I've tried multiple ways of adding the disco-2.0.jar file to the build path but I'm not sure if that's what I'm meant to be doing or if it's even the right file, although I haven't found any other disco file within the project directories.
I've tried mvn clean install -U to see if it may just have been a problem with resetting the maven project.

Well the log reads is clear and you could verify it as well:
Failure to find com.disco:disco:jar:10.2.0 in http://clojars.org/repo
If you navigate to the https://clojars.org/repo/com/ there is no disco.jar available there. Hence the failure.
Probably this could be some local jar that might need to be build either locally or required by its owner to be pushed(mvn deploy) to clojars in another case.
Also mvn clean install -U help you fetch the latest of SNAPSHOT, in your case this would fetch the latest tornado:tornado:jar:0.0.1-SNAPSHOT but that fails further sicne it specifies the com.disco:disco:jar:10.2.0 as dependency which is not found anywhere for your build to proceed.

You need to make the disco-2.0.jar available from a Maven repository. If you have a Nexus or Artifactory, upload it there. Alternatively, you can install it into the local repository of your computer using the install:install-file goal.
Furthermore, it is possible to define local directories as additional Maven repositories, see https://stackoverflow.com/a/28762617/927493.

What does it mean in Maven when it says the following artifacts could not be resolved although they are in Maven cache?

I get the following error:
The following artifacts could not be resolved: com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1: Failure to find com.sun.jdmk:jmxtools:jar:1.2.1 in https://artifactory.corp.adobe.com/artifactory/maven-identity-snapshot was cached in the local repository, resolution will not be reattempted until the update interval of artifactory-snapshot
However, both jars are in the Maven cache (.m2 folder) on my machine. I mean files named: jmxri-1.2.1.jar and jmxtools-1.2.1.jar. They are respectively in the folders com/sun/jmdk/jmxtools/1.2.1/ and com/sun/jmx/jmxri/1.2.1
EDIT: When I try the -o switch on Maven to force it to use the local jars, it says the artifact has not been downloaded before. Which is probably true since indeed the artifact is not in the repo but was copied from some other place to my Maven cache -- is it possible to force Maven to use the jars? The -o switch does not seem to force this and Maven seems to be able to detect that the artifact was not downloaded.

Try to delete corresponding artifact folders in maven local repo and rerun or just rerun using -U flag.
Which is probably true since indeed the artifact is not in the repo but was copied from some other place to my Maven cache
Manually copying jars is not the correct way to put artifacts into maven local repo. You should use mvn install:install-file instead. More details here: Guide to installing 3rd party JARs

The dependency on those jars is usually a consequence of a bug in the pom.xml for log4j 1.2.15.
Update to 1.2.16 or 1.2.17 and you will not need these jars any longer.
These particular artefacts date back to a time when Sun licensing did not permit the hosting of the actual jars in a public maven repository.
You were required to accept licence conditions, download them yourself and then manually install either into your local repo (using mvn install:install-file) or into your corporate repository manager (typically using a UI that it provides or mvn deploy:deploy-file).

ArtifactTransferException:

Failed to execute goal on project J2EE2: Could not resolve
dependencies for project com.example.j2ee2:J2EE2:war:0.0.1-SNAPSHOT:
The following artifacts could not be resolved: javax.jms:jms:jar:1.1,
com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1: Could
not transfer artifact javax.jms:jms:jar:1.1 from/to java.net
(https://maven-repository.dev.java.net/nonav/repository): No connector
available to access repository java.net
(https://maven-repository.dev.java.net/nonav/repository) of type
legacy using the available factories AsyncRepositoryConnectorFactory,
WagonRepositoryConnectorFactory
I've updated all my "lastUpdated" files, still I'm repeatedly getting the same error all the time. Is this error arising because I don't have setting.xml in my .m2?

Either one of the options:
1 - This repository that your configuration is trying to download the dependency doesn't exists (https://maven-repository.dev.java.net/nonav/repository)
2 - You are in a machine under a proxy and it is not configured in your maven settings.xml file (whether it is on .m2 or $MAVEN_HOME/conf )
3 - See if your eclipse is usign the maven installation or the embeded maven installation (change to maven installation)
Hope it help