- This topic has 5 replies, 4 voices, and was last updated 14 years, 6 months ago by
.
-
Posts
-
Any progress on this front? Is there an option in MyEclipse Maven to ACTUALLY support Maven and not some FOOLS personal Frankenstein?
I just downloaded MyEclipse 8.0 with hopes that Maven support would be fixed. Unfortunately, it continues with the same absurd notion of ignoring convention in supporting a feature that is fundamentally about Convention over Configuration (CoC). MyEclipse is increasingly bloated and in need of a feature for turning off features. Adding to it a Maven feature that gets in the way of actually using Maven and I have had it. I am not renewing my license and I will start from scratch. When I use Maven I want to use it for what it was designed for. If the MyEclipse people want to start an alternative random project that competes with Maven then they should do that. If they don’t have the guts to put out and let the development community choose between their version and Maven’s then I suggest they stand down, show some Humility over Hubris and support Maven as it is designed and accepted (or sometimes admittedly not).
Hi,
I have escalated this to the dev team member, they will get back to you on this.
Thanks,
Chakri.Bob,
MyEclipse is increasingly bloated and in need of a feature for turning off features
MyEclipse 8.5 has a Software and workspace configuration center which allows you to completely uninstall parts you don’t need. In fact, we also have a web installer which you can see here: http://myeclipseide.com/installer/ which will help you download just the components you need.
I am taking a fresh look at our Maven integration going forward. In 8.5, we refreshed our Maven support and updated our internal version of m2Eclipse to 0.10.0. This should improve the general Maven experience significantly. 8.0 had no significant changes in the Maven department, for your point of view, it would be pretty close to our early integrations.
On to CoC – I realize MyEclipse Maven Web projects are not setup in a “Maven” way. Before we go on to discuss this in detail, is this what you have a problem with? As far as “regular” Maven projects are concerned, you are free to create whatever project structure you desire and I know we don’t change the functionality that supports a completely flexible structure. Of course, these will not work as MyEclipse Web Projects and this is something we are aware of and trying to address.
If you have other problems, can you please let me know what they are or point me to threads in which you have already discussed them? I will take these into account for subsequent MyEclipse versions and I’m sorry you have had such a bad time with the tooling so far.
