- This topic has 1 reply, 2 voices, and was last updated 15 years, 1 month ago by
.
-
Posts
-
If I understand it correctly, the “maven4myeclipse” plugin is labeled as a “custom” version of “m2eclipse” plugin. I was curious to know what were the factors that led to the decision to write a custom version of “m2eclipse” as opposed to simply allow users to “m2eclipse” plugin as is.
@phibei wrote:
If I understand it correctly, the “maven4myeclipse” plugin is labeled as a “custom” version of “m2eclipse” plugin. I was curious to know what were the factors that led to the decision to write a custom version of “m2eclipse” as opposed to simply allow users to “m2eclipse” plugin as is.
We had to do some refactorings to m2eclipse to make it possible to implement the tight integration with MyEclipse project support and UI. We also fixed some issues that could’ve caused problems to our users (i.e. we let the user to use different Java runtime for Maven from the one that is used to run MyEclipse with). And, as with most other OSS projects we integrate with, there are many bugfixes that noone will notice since they are fixed 😉
