|
Dependencies are fine with m2eclipse I have the same problem. This patch works perfectly for me. This is a nasty bug and it's already fixed. So when is the release of the eclipse-plugin with bugfixes? This bug isn't fixed and I cannot apply Bertrand's patch because it will require that you build your project before launching eclipse:eclipse. What I have in mind is to have a look at the code in the dependency:list mojo to try to reuse/recopy it. I'm sorry to have to say that but if dependency resolution which in my opinion should the core of maven does not get implemented there once but gets copied between all the plugins depending on it then maven has failed. Reuse is one othe the basics of software engineering. Actually in maven 2.0.x, we can reuse the depdency mechanism from the core because there is no possibility to ask to maven to not resolve dependencies in the reactor. If we use the standard resolution mechanism you'll not be able to call an eclipse:eclipse goal if your project cannot be built. We are aware of this issue and are trying to solve it. But in the plugin to keep the compatibilility with 2.0.X we have to find a workaround. You meant "can't" in the start of your comment, not "can", right? yes, "can't", sorry. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The number of dependencies is also wrong.
For example, we have a project with those dependencies :
The tree of dependencies is :
But in the .classpath we have :