| [m2e-users] Connection refusal connecting to nexus from eclipse luna, while successful in kepler |
|
I'd been working with Eclipse Kepler. I had several Maven projects
there. I connected to Maven Central through a corporate Nexus
repository. Everything worked just fine. Then I got Eclipse Luna and installed it. Using the SAME workspace, with the same maven settings.xml that had the settings for the Nexus repository, I find that all Maven projects show errors that cannot be resolved by running Maven->Update. All mention something about connections being refused by Maven Central. I closed Eclipse Luna and restarted Kepler on the same workspace. (I was never running them simultaneously). The same errors appeared, but now Maven->Update was successful in resolving them. I closed Kepler and restarted Luna on the same workspace. Once again, the errors returned, and were not resolvable by Maven->Update. Here is one of the errors: CoreException: Could not get the value for parameter compilerId for plugin execution default-compile: PluginResolutionException: Plugin org.apache.maven.plugins:maven-compiler-plugin:3.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-plugin-api:jar:2.0.9, org.apache.maven:maven-artifact:jar:2.0.9: Failure to transfer org.apache.maven:maven-plugin-api:jar:2.0.9 from http://mavencentral.it.whatever.com:8084/nexus/content/groups/whatever-public-group 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 artifact org.apache.maven:maven-plugin-api:jar:2.0.9 from/to nexus (http://mavencentral.it.whatever.com:8084/nexus/content/groups/whatever-public-group): Connection refused: connect What might the problem be? |