maven-dependency-plugin goals copy-dependencies unpack is not supported by m2e

Question

I have a fairly simple Maven project    lt project gt       lt dependencies gt                   lt  dependencies gt        lt build gt           lt plugins gt               lt plugin gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                   lt version gt 2 4 lt  version gt                   lt executions gt                       lt execution gt                           lt id gt copy-dependencies lt  id gt                           lt phase gt package lt  phase gt                           lt goals gt                               lt goal gt copy-dependencies lt  goal gt                           lt  goals gt                           lt configuration gt                               lt outputDirectory gt   project build directory  dependencies lt  outputDirectory gt                           lt  configuration gt                           lt  execution gt                   lt  executions gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt    However  I get the following error in m2eclipse   Description Resource    Path    Location    Type maven-dependency-plugin  goals  copy-dependencies    unpack   is not supported by m2e  pom xml   jasperreports-test line 60 Maven Project Build Lifecycle Mapping Problem   Why do I care if m2eclipse doesn t  support  this task  Maven does  and that s all I really care about  How can I get this error in my project to go away

User · Answer

To make it work  instead of ignoring it  you can install the m2e connector for the maven-dependency-plugin  https   github com ianbrandt m2e-maven-dependency-plugin  Here is how you would do it in Eclipse    go to Window Preferences Maven Discovery  enter Catalog URL  http   download eclipse org technology m2e discovery directory-1 4 xml click Open Catalog choose the m2e-maven-dependency-plugin enjoy

User · Answer

It seems to be a known issue  You can instruct m2e to ignore this    Option 1  pom xml  Add the following inside your  lt build  gt  tag    lt pluginManagement gt   lt plugins gt       lt  -- Ignore Execute plugin execution -- gt       lt plugin gt           lt groupId gt org eclipse m2e lt  groupId gt           lt artifactId gt lifecycle-mapping lt  artifactId gt           lt version gt 1 0 0 lt  version gt           lt configuration gt               lt lifecycleMappingMetadata gt                   lt pluginExecutions gt                       lt  -- copy-dependency plugin -- gt                       lt pluginExecution gt                           lt pluginExecutionFilter gt                               lt groupId gt org apache maven plugins lt  groupId gt                               lt artifactId gt maven-dependency-plugin lt  artifactId gt                               lt versionRange gt  1 0 0   lt  versionRange gt                               lt goals gt                                   lt goal gt copy-dependencies lt  goal gt                               lt  goals gt                           lt  pluginExecutionFilter gt                           lt action gt                               lt ignore   gt                           lt  action gt                       lt  pluginExecution gt                   lt  pluginExecutions gt               lt  lifecycleMappingMetadata gt           lt  configuration gt       lt  plugin gt      lt  plugins gt  lt  pluginManagement gt    You will need to do Maven    -  Update Project Configuration on your project after this   Read more  http   wiki eclipse org M2E plugin execution not covered m2e maven plugin coverage status  Option 2  Global Eclipse Override  To avoid changing your POM files  the ignore override can be applied to the whole workspace via Eclipse settings   Save this file somewhere on the disk  https   gist github com maksimov 8906462  In Eclipse Preferences Maven Lifecycle Mappings browse to this file and click OK

User · Answer

I had the same problem when trying to load Hadoop project in eclipse  I tried the solutions above  and I believe it might have worked in Eclipse Kepler    not even sure anymore  tried too many things     With all the problems I was having  I decided to move on to Eclipse Luna  and the solutions above did not work for me    There was another post that recommended changing the     tag to package  I started doing that  and it would  clear  the errors    However  I start to think that the changes would bite me later - I am not an expert on Maven    Fortunately  I found out how to remove all the errors  Go to Window- Preferences- Maven-  Error Warnings and change  Plugin execution not covered by lifecycle     option to  Ignore   Hope it helps

User · Answer

This is a problem of M2E for Eclipse M2E plugin execution not covered   To solve this problem  all you got to do is to map the lifecycle it doesn t recognize and instruct M2E to execute it   You should add this after your plugins  inside the build  This will remove the error and  make M2E recognize the goal copy-depencies of maven-dependency-plugin and make the POM work as expected  copying dependencies to folder every time Eclipse build it  If you just want to ignore the error  then you change  lt execute   gt  for  lt ignore   gt   No need for enclosing your maven-dependency-plugin into pluginManagement  as suggested before    lt pluginManagement gt     lt plugins gt       lt plugin gt         lt groupId gt org eclipse m2e lt  groupId gt         lt artifactId gt lifecycle-mapping lt  artifactId gt         lt version gt 1 0 0 lt  version gt         lt configuration gt           lt lifecycleMappingMetadata gt             lt pluginExecutions gt               lt pluginExecution gt                 lt pluginExecutionFilter gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                   lt versionRange gt  2 0   lt  versionRange gt                   lt goals gt                     lt goal gt copy-dependencies lt  goal gt                   lt  goals gt                 lt  pluginExecutionFilter gt                 lt action gt                   lt execute   gt                 lt  action gt               lt  pluginExecution gt             lt  pluginExecutions gt           lt  lifecycleMappingMetadata gt         lt  configuration gt       lt  plugin gt     lt  plugins gt   lt  pluginManagement gt

User · Answer

I know this is old post but I struggled today with this problem also and I used template from this page  http   maven apache org plugins maven-dependency-plugin usage html   lt project gt             lt build gt       lt plugins gt         lt plugin gt           lt groupId gt org apache maven plugins lt  groupId gt           lt artifactId gt maven-dependency-plugin lt  artifactId gt           lt version gt 2 7 lt  version gt           lt executions gt             lt execution gt               lt id gt copy lt  id gt               lt phase gt package lt  phase gt               lt goals gt                 lt goal gt copy lt  goal gt               lt  goals gt               lt configuration gt                 lt artifactItems gt                   lt artifactItem gt                     lt groupId gt   groupId   lt  groupId gt                     lt artifactId gt   artifactId   lt  artifactId gt                     lt version gt   version   lt  version gt                     lt type gt   packaging   lt  type gt                     lt classifier gt   classifier - optional   lt  classifier gt                     lt overWrite gt   true or false   lt  overWrite gt                     lt outputDirectory gt   output directory   lt  outputDirectory gt                     lt destFileName gt   filename   lt  destFileName gt                   lt  artifactItem gt                 lt  artifactItems gt                 lt  -- other configurations here -- gt               lt  configuration gt             lt  execution gt           lt  executions gt         lt  plugin gt       lt  plugins gt     lt  build gt           lt  project gt    and everything works fine under m2e 1 3 1   When I tried to use    lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-dependency-plugin lt  artifactId gt               lt version gt 2 4 lt  version gt               lt executions gt                   lt execution gt                       lt id gt copy-dependencies lt  id gt                       lt phase gt package lt  phase gt                       lt goals gt                           lt goal gt copy-dependencies lt  goal gt                       lt  goals gt                       lt configuration gt                           lt outputDirectory gt   project build directory  dependencies lt  outputDirectory gt                       lt  configuration gt                       lt  execution gt               lt  executions gt           lt  plugin gt       lt  plugins gt   lt  build gt    I also got m2e error

User · Answer

Another option is to navigate to problems tab  right click on error  click apply quick fix  The should generate the ignore xml code and apply it  pom file for you

User · Answer

Despite answer from CaioToOn above  I still had problems getting this to work initially    After multiple attempts  finally got it working  Am pasting my final version here - hoping it will benefit somebody else        lt build gt            lt plugins gt               lt  --             Copy all Maven Dependencies  -MD  into libMD  folder to use in classpath via shellscript              -- gt                lt plugin gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-dependency-plugin lt  artifactId gt                   lt version gt 2 8 lt  version gt                   lt executions gt                       lt execution gt                           lt id gt copy lt  id gt                           lt phase gt package lt  phase gt                           lt goals gt                               lt goal gt copy-dependencies lt  goal gt                           lt  goals gt                           lt configuration gt                               lt outputDirectory gt   project build directory  libMD lt  outputDirectory gt                           lt  configuration gt                       lt  execution gt                   lt  executions gt               lt  plugin gt           lt  plugins gt           lt  --           Above maven-dependepcy-plugin gives a validation error in m2e           To fix that  add the plugin management step below  Per  http   stackoverflow com a 12109018         -- gt           lt pluginManagement gt               lt plugins gt                   lt plugin gt                       lt groupId gt org eclipse m2e lt  groupId gt                       lt artifactId gt lifecycle-mapping lt  artifactId gt                       lt version gt 1 0 0 lt  version gt                       lt configuration gt                           lt lifecycleMappingMetadata gt                               lt pluginExecutions gt                                   lt pluginExecution gt                                       lt pluginExecutionFilter gt                                           lt groupId gt org apache maven plugins lt  groupId gt                                           lt artifactId gt maven-dependency-plugin lt  artifactId gt                                           lt versionRange gt  2 0   lt  versionRange gt                                           lt goals gt                                               lt goal gt copy-dependencies lt  goal gt                                           lt  goals gt                                       lt  pluginExecutionFilter gt                                       lt action gt                                           lt execute   gt                                       lt  action gt                                   lt  pluginExecution gt                               lt  pluginExecutions gt                           lt  lifecycleMappingMetadata gt                       lt  configuration gt                   lt  plugin gt               lt  plugins gt           lt  pluginManagement gt       lt  build gt

User · Answer

If copy-dependencies  unpack  pack  etc   are important for your project you shouldn t ignore it  You have to enclose your  lt plugins gt  in  lt pluginManagement gt  tested with Eclipse Indigo SR1  maven 2 2 1

[eclipse] maven-dependency-plugin (goals "copy-dependencies", "unpack") is not supported by m2e

Examples related to eclipse

Examples related to maven

Examples related to m2eclipse