Version InformationMaven 3.0.4
The ProblemTo run Maven offline, you need to use the -o argument or set offline to true in settings.xml. I assumed that would be all that's necessary, but I kept getting the following errors for third-party jars that I added to our Nexus repo at work:
Failure to find blah 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]
Failed to execute goal on project blah : Could not resolve dependencies for project
The following artifacts could not be resolved
[WARNING] The POM for blah is missing, no dependency information available
The repository system is offline but the artifact blah is not available in the local repository.
The ReasonAfter an entire day of tracking down the problem online, I finally stumbled upon the reason for all the issues described in these three articles.
To quote the first one:
"Thank you. That was the problem. I had had a setting.xml that pointed to
an internal repo at my company, and then cleared it out. Maven puts a
file named _maven.repositories in with the jar file in the local repo
that keeps track of where the jar came from. If the remote repo isn't
available, the build fails. Deleting _maven.repositories solved the
This seems like an extrordinarily bad design. If a remote system goes
down, you can't do a build? If you have an internal repo at work, and
you take your laptop home, you can't do a build?"