[m2e-users] Proxy settings defined in settings.xml not used by maven m2e

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[m2e-users] Proxy settings defined in settings.xml not used by maven m2e?

From: Markus Kopyciok <mkopyciok@xxxxxxxxx>
Date: Tue, 14 Feb 2017 12:40:53 +0100
Delivered-to: m2e-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-users>
List-help: <mailto:m2e-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=unsubscribe>

Dear all,

I came across some problems regarding the proxy configuration used by
m2e in Eclipse. When creating a new maven project from the scratch the
build fails and I receive from eclipse the error message:

   Could not calculate build plan: Plugin
org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
   Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one
of its dependencies could not be resolved: Failed to read artifact
descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6

Neither a successful maven project build without previous archetype
selection nor any with archetype selection is possible. In Eclipse's
New Maven project wizard for my configured remote catalog no
archetypes are listed. I configured the remote repository in
Eclipse>Preferences>Maven>Archetypes which is
https://repo1.maven.org/maven2/archetype-catalog.xml (also tried
different). In this dialog when pressing the verify button the error
message "Remote catalog is empty" is returned.

In order to fix the problem, I goggled a little bit around and
verified that my proxy settings in settings.xml are the same as in the
eclipse>preferences>network connections (accessing e.g. Eclipse
Marketplace via the indicated proxy works fine). Furthermore, I also
deleted the existing local user repository saved under
C:\Users\<username>\.m2\repository in order to force an update of the
project with accurate dependencies.

I am running on

   - Eclipse Java EE IDE for Web Developers, Version: Neon.2 Release
(4.6.2), Build id: 20161208-0600
   - Maven Integration for Eclipse, Version 1.7.0-20160603-1933 (the
embedded one)
   - http proxy which user authorisation

My guess is that m2e is not using the proxy settings indicated in the
settings.xml file. Do you have any ideas how to fix this problem or
should I report a bug?

In detail, the java stack trace is:

org.apache.maven.plugin.PluginResolutionException: Plugin
org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:284)
at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:961)
at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException:
Failed to read artifact descriptor for
org.apache.maven.plugins:maven-resources-plugin:jar:2.6
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
... 35 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException:
Failure to transfer
org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from
https://repo.maven.apache.org/maven2 was cached in the local
repository, resolution will not be reattempted until the update
interval of central has elapsed or updates are forced. Original error:
Could not transfer artifact
org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to
central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267)
... 38 more
Caused by: org.eclipse.aether.transfer.ArtifactTransferException:
Failure to transfer
org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from
https://repo.maven.apache.org/maven2 was cached in the local
repository, resolution will not be reattempted until the update
interval of central has elapsed or updates are forced. Original error:
Could not transfer artifact
org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to
central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
... 41 more

Best
Markus

Prev by Date: Re: [m2e-users] Building m2e plugin
Next by Date: [m2e-users] Issue with maven-dependency-plugin's copy mojo and m2e
Previous by thread: [m2e-users] Building m2e plugin
Next by thread: [m2e-users] Issue with maven-dependency-plugin's copy mojo and m2e
Index(es):
- Date
- Thread

Breadcrumbs