- This topic has 1 reply, 2 voices, and was last updated 16 years, 1 month ago by
.
-
Posts
-
This is a horrible re-jiggering of M2Eclipse. Many things that work in M2Eclipse are absent or missing from your fork. Please work on extending and integrating with M2Eclipse and cancel your fork of the code. You should be working with this open source project for the betterment of both, not taking their code and delivering a half working version of it while preventing the original version from running.
All of our current 50 licenses are still on Eclipse 6.0 since latter MyEclipse versions do not work with M2Eclipse. If M2Eclipse support is not restored, our 50 licenses will most regrettably be leaving MyEclipse.
I have taken the liberty of taking a screenshot of this post. I’m very disappointed with how Genuitec has chosen to implement Maven support, and will do everything in my power to encourage Genuitec to take a more community oriented approach in bringing Maven into the fold. There is already some outrage in the MyEclipse community, posts such as those of Jason van Zyl, expressing how badly Maven4Eclipse and 6.5 and onwards incompatibility with M2Eclipse has hurt MyEclipse customers.
Overall our company has been very pleased with MyEclipse, but this project has erected a huge barrier to our continued usage.
regards,
rektiderektide,
Maven4MyEclipse was introduced in 6.5 to provide the very basic Maven functionality. I agree Maven4MyEclipse does not provide the advanced functionality like M2Eclipse but we are working on adding new features to Maven4MyEclipse. In the mean time, the Maven4MyEclipse – M2Eclipse incompatibility issue that existed in 6.5 has been resolved in the MyEclipse 7.0 release. The users who are comfortable working with M2Eclipse can continue working with M2Eclipse along side Maven4MyEclipse.I’m sorry for the inconvenience caused but I can assure you that we are going to be adding more functionality to Maven4MyEclipse as we move forward.
