Skip to main content

Maven Error: Failed to resolve POM

After downloading Maven M2 Plug-in, My first build gave me this error. Just so annoying. It kept breaking at.

Failed to resolve POM for org.apache.maven.doxia:doxia:1.0-alpha-7 due to Missing:
----------
1) org.apache.maven.doxia:doxia:pom:1.0-alpha-7
----------
1 required artifact is missing.
This could also happen to other POMs. doxia is just an example. The direct log indicated it could not find anything from
central (http://repo1.maven.org/maven2, releases=true, snapshots=false),
plexus.snapshots (http://oss.repository.sonatype.org/content/repositories/plexus-snapshots, releases=false, snapshots=true), 
apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true) 

But it clearly exists in
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.4.1:resources (default-resources) on project iwe: Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:2.4.1:resources failed: Plugin org.apache.maven.plugins:maven-resources-plugin:2.4.1 or one of its dependencies could not be resolved: Unable to get dependency information for org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7: Failed to process POM for org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7: Non-resolvable parent POM org.apache.maven.doxia:doxia:1.0-alpha-7 for org.apache.maven.doxia:doxia-sink-api:1.0-alpha-7: Failed to resolve POM for org.apache.maven.doxia:doxia:1.0-alpha-7 due to Missing:
----------
1) org.apache.maven.doxia:doxia:pom:1.0-alpha-7
----------
1 required artifact is missing.

for artifact: 
org.apache.maven.doxia:doxia:pom:1.0-alpha-7

from the specified remote repositories:
central (http://repo1.maven.org/maven2, releases=true, snapshots=false),
plexus.snapshots (http://oss.repository.sonatype.org/content/repositories/plexus-snapshots, releases=false, snapshots=true),
apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true)
-> [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


Full log available @ http://sar.pastebin.com/raw.php?i=nvfyJ40S

Apparently The solution is found, least expectedly, in the last URL (in the comments, aamof). By the nature and verbiage of the output, we keep looking under repo1.maven.org/maven2, but will have to eventually, lose to mild to extreme annoyance. The URL again, lists out all the different reasons a dependency resolution may fail, except this particular case. Thanks to Matthew McCullough, the actual problem can be solved by merely deleting the .lastUpdated file.
If the artifact is either found or not found, a file is written to your ~/.m2/repository of the format myfavoritetool-plugin-2.0.4.maven-plugin.lastUpdated that keeps track of the fact that a remote repo was asked for this artifact.

Once this file is written, remote sites are NOT checked again for updates. To force a check of remote sites for updates to releases OR snapshots of traditional artifacts AND plugin artifacts, issue the -U flag to Maven. This is, in long form, called --update-snapshots, but truly updates both releases and snapshots. I'm submitting a patch to remove mention of --update-snapshots from the mvn -h help output. This patch was submitted as http://jira.codehaus.org/browse/MNG-4537

Unfortunately, the page was not found during my relentless Googling.It pays to read the comments sometimes. Someone needs to update the page.

Popular posts from this blog

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour