Description Tobias Oberlies 2011-10-21 07:56:50 EDT

For a reason that I don't understand, m2eclipse particularly seems to dislike the maven-dependency-plugin. For a project in which I have configured the unpack goal, I get the error "maven-dependency-plugin (goals "copy-dependencies", "unpack") is not supported by m2e."

This message leaves me with several questions:

- If the maven-dependency-plugin goals are not supported, why are these goals not just disabled? I am quite sure that m2eclipse doesn't support the deploy plugin either, but I'm not seeing an error for that.

- If m2eclipse doesn't know what to do with the goals, why doesn't it offer a quick fix to let me specify what to do. m2eclipse does this for other unknown goals. I can make the error go away by copying the ignore mapping from a different plugin, but why does this have to be a manual thing?

- What does m2eclipse mean by "not supported"? In the same way as I can ignore the plugin, I can also make m2eclipse execute it. This is for example used in this project [1], and except for the manual refresh needed afterwards, this works very well.

[1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-surefire/org.eclipse.tycho.surefire.junit/pom.xml