On 14/06/2011 15:19, Matthew Piggott wrote:
If you right-click on the line with the error in
Eclipse, is there a Quick Fix which allows you to ignore the
error?
There is no quick fix offered unlike the other similar errors we got
for our own plugins. However I did get rid of the error by manually
adding the required entry in my parent pom.
I don't believe we've written any documentation at
this point, the source for most of the plugins we've written is
available in Github @ https://github.com/sonatype/m2eclipse-extras
. Also, if you search the history of both mailing lists (m2e-dev
is the other) there should be a few threads with Benson Margulies
as he was writing two.
Okay, thanks
Matthew
On 14 June 2011 10:06, Paul French <paul.french@xxxxxxxxxx>
wrote:
I get this error in eclipse
maven-dependency-plugin (goals "copy-dependencies",
"unpack") is not supported by m2e
I've removed other m2e errors caused by our own plugins by
configuring the...
<pluginManagement>
<plugins>
<!--This plugin's configuration is used to store Eclipse
m2e settings only. It has no influence on the Maven build
itself.-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
...etc
So, any ideas how to get rid of the error above?
Any docs/wiki post on how to write/supply your own m2e
connector for your own plugins so the bespoke part of your
builds integrate nicely with the eclipse build ? (that is my
understanding ??)
Ta
P
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
|