The two problems are most likely unrelated.
m2e used to claim maven-plugin-plugin support. This was a left-over from
some experiments we ran during 1.0 development and was never meant to be
permanent part of m2e core. I cleaned up this leftover configuration in
1.5M4. If you need proper maven-plugin development support inside
Eclipse workspace, have a look at [1] I published few weeks ago. If you
just want to make the error marker go away, use quick-fix to ignore the
plugin in pom.xml or eclipse workspace.
Failure to transfer maven-plugin-plugin:3.2 appears to suggest a problem
with your nexus configuration. Make sure the plugin jar and pom
artifacts are available in Nexus and talk to your Nexus admins if they
don't.
[1] https://github.com/ifedorenko/com.ifedorenko.m2e.mavendev
--
Regards,
Igor
On 12/23/2013, 11:03, Stanimir Stamenkov wrote:
Wed, 18 Dec 2013 07:47:10 -0500, /Igor Fedorenko/:
I just published 1.5/Luna M4 milestone build, exact version is
1.5.0.20131218-1208 to m2e milestone repository.
This bugzilla query returns fixes and improvements since M3
https://bugs.eclipse.org/bugs/buglist.cgi?list_id=7776607&query_format=advanced&product=m2e&target_milestone=1.5.0%2FLuna%20M4
Milestone repository URL and installation instructions are available on
m2e download page
http://eclipse.org/m2e/download/
After updating from m2e 1.5 M3, I've started getting Maven Project
Build Lifecycle Mapping Problem:
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor (execution:
default-descriptor, phase: generate-resources)
for projects with <packaging>maven-plugin</packaging> – is it
expected?
When using the corporate "settings.xml" which refers to an internal
repository/mirror (Nexus), I'm also getting Maven Configuration
Problem:
Failure to transfer org.apache.maven.plugins:maven-plugin-plugin:pom:3.2 from
http://<my_company_repo> was cached in the local repository, resolution will not be
reattempted until the update interval of internal-mirror has elapsed or updates are forced.
Original error: Could not transfer artifact org.apache.maven.plugins:maven-plugin-plugin:pom:3.2
from/to internal-mirror (http://<my_company_repo>): <my_company_repo_host>
which ends up with the following Maven Project Update Problem:
Could not calculate build plan: Plugin
org.apache.maven.plugins:maven-plugin-plugin:3.2 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.apache.maven.plugins:maven-plugin-plugin:jar:3.2
Plugin org.apache.maven.plugins:maven-plugin-plugin:3.2 or one of its
dependencies could not be resolved: Failed to read artifact descriptor for
org.apache.maven.plugins:maven-plugin-plugin:jar:3.2
Does the former issue appear related to the later?
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
