Sometimes Maven takes heat for being "opinionated" and wanting you to do things in a certain way. Even though it is usually configurable, it's normally easier to go with the flow.
It seems the "Maven Way" is catching on, as masses of Maven users rebel against MyEclipse's attempt to use M2Eclipse as the basis for their Maven integration. In the beginning, it sounded like a good thing, using the best plugin as a base to provide integration to more users. The trouble is that this implementation changed some core functionality and only supports new projects. Worse is that the incompatibility trips up existing M2e users with the Maven4Eclipse implementation.
A key tenet of Maven is that all Maven based projects behave the same regardless of where they are. Once you know Maven, you should work with any Maven project in seconds. It seems MyEclipse broke this tenet, and the users aren't too happy about it.
A more appropriate approach would be to work with M2e to add features instead of effectively forking it.
.jpg?width=150&height=150&name=fox-2016-1-sq%20(1).jpg)
Brian Fox, CTO and co-founder of Sonatype, is a Governing Board Member for the Open Source Security Foundation (OpenSSF), a Governing Board Member for the Fintech Open Source Foundation (FINOS), a member of the Monetary Authority of Singapore Cyber and Technology Resilience Experts (CTREX) Panel, a ...
Explore All Posts by Brian FoxTags
Discover a Better Way to SCA
Forrester evaluated 10 SCA providers and recognized Sonatype with the highest possible scores. Learn why Sonatype was named a leader in Forrester Wave™ for SCA.
