I'm using nexus to host my maven repository, and maven command line (both win32 and linux) can transfer artifacts from this nexus successfully, using same command and same setting.xml. But m2e will fail as follows:
[WARNING] Could not transfer metadata m3-app:m3:1.0-SNAPSHOT/maven-metadata.xml from/to Nexus (http://1.2.3.4:8080/nexus/content/groups/public): Failed to create a selector. to http://1.2.3.4:8080/nexus/content/groups/public/m3-app/m3/1.0-SNAPSHOT/maven-metadata.xml
[WARNING] Failure to transfer m3-app:m3:1.0-SNAPSHOT/maven-metadata.xml from http://1.2.3.4:8080/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of Nexus has elapsed or updates are forced. Original error: Could not transfer metadata m3-app:m3:1.0-SNAPSHOT/maven-metadata.xml from/to Nexus (http://1.2.3.4:8080/nexus/content/groups/public): Failed to create a selector. to http://1.2.3.4:8080/nexus/content/groups/public/m3-app/m3/1.0-SNAPSHOT/maven-metadata.xml
I've tested the server while eclipse failing to grab artifact, and my browser can get the metadata xml successfully. Is there any problem with m2e?
Update: my project includes about 35 jars, first several jars will succeed, and later it will fail.
Solution found: Disable Avira Web guard, and everything looks fine, running in eclipse just as running in command line. Considering change another anti virus solution...
来源：https://stackoverflow.com/questions/15020441/m2e-cannot-transfer-metadata-from-nexus-but-maven-command-line-can