I had a similar problem from the Maven command line. In the end, I walked past this error by adding -U to the maven arguments.
Depending on how you configured your source repository in your settings.xml file, sometimes Maven cannot load a particular artifact, so it assumes that the artifact cannot be loaded, even if you change some settings that Maven will give for the artifact if he just tried. -U makes Maven look again.
Now you need to make sure that the Maven artifact is looking in at least one of the repositories that your settings.xml is referencing. To know for sure, run
mvn help:effective-settings
from the directory of the module you are trying to build. This should give you, among other things, a complete list of repositories that you use Maven to search for the artifact.
John Chesshir Aug 29 '16 at 21:55 2016-08-29 21:55
source share