There is a well-known problem with Eclipse m2e maven plugin - it neither uses Eclipse' proxy settings nor system proxy settings. Well-known solution is to put correct proxy definitions
BOTH in system's mvn config (mine is at /usr/share/maven/settings.xml)
AND in user's local mvn config (mine is at /home/
myname/.m2/settings.xml)
Then in Eclipse Window-Preferences-Maven-User Settings you need to specify correct paths to both those settings.xml configs and it works -
with one critical exception.
Maven fails to access the remote archetype repository - neither system's mvn (mine is Apache Maven 3.0.5) nor Eclipse m2e plugin (mine is 3.2.3/1.6.0.20140823-0915 but earlier one didn't work either).
After 1,5 days of attempts, it turned out that while Maven correctly uses proxy (if correctly configured) for ALMOST everything with a single exception - archetype access.
Both system mvn and m2e plugin started working with archetypes only after
- I forced sysadmins to create a "hole" in the proxy for site app.camunda.org,
- added app.camunda.com to "no proxy hosts" lists in 3 configs: system's mvn, my local mvn config and eclipse preferences.
Hope this will save someone (who apparently is the same proxy victim as me) some time and effort.
WBR,
Andrii