Configuring a Maven project via POM, project properties, preferences, archetype XM in metadataL, etc. gets very difficult to match to an already extant Maven project. A good, usable and complete Maven project settings which includes lifecycle mappings would help a lot.

edit and refact js better

Whenever you set your project to a certain version of a facet, MyEclipse should be able to allow you to change the version. Example. (Changing from JSF 2.0 to 2.2 facet.)

It should give you all the problems your project may have after you change so you can upgrade projects quickly.

format html/jsp/js better

The .metadata folder for a moderately sized maven projects can reach almost 2GB, probably more for large projects. On a PC with a SSD and limited HDD Space that is outragous. It would be nice if that folder could be made smaller (Also a UI option to cleanup the cached files could be helpful.)

A common painful task is creating multiple named instances of the same server. I just did this for MyEclipse 2014 where I needed a WebTier instance of Tomcat and a MidTier instance, each listening on their own ports. The current MyEclipse plugin does not support this but it can be done through the Run Configuration. Actually, once I figured it out it was not to difficult but I'm sure I will have forgotten it by the time I upgrade to the next release

Round-trip Java / UML techniques are quite useful in agile projects, and basic Java beans generally work quite well - but as soon as we start using Java annotations, things get dropped / missed / messed up and must be reconciled manually.

Although the list of running threads within a Remote Java Application in the Debug panel is great, it would be nice to allow for easier labeling of the threads from within code, memory utilization and overall better visualization in real time.

Being able to select a folder, right click and select exclude from options is a great feature. It would be great for it to remain in force a project clean. After a clean, in order to make it take affect again, one needs to uncheck it and then check it again. I think this is also a problem after closing a project and reopening it.

I would like the default editor for JSF pages be the MyEclipse JSF Editor. I find the current visual edtior to be slow and does not provide additional useful content.

Provide a WYSIWIG edtior for the Markdown format. http://en.wikipedia.org/wiki/Markdown

a) generate class (immutable w/constructor or mutable bean) from java interface

b) generate java interface file when methods of the class marked "final"

c) keyboard shortcuts for all source and refactoring commands, not just some of them

Provide a view that allows templates to be changed or created by highlighting the desired text, right click and create template. Then be able to add options for prompting of values. See http://docs.activestate.com/komodo/8.0/snippets.html. Komodo's model for managing snippets is awesome and the [[%ask:Name:default]] ability makes for huge productivity gains. Being able to put templates into folders within the view would help immensely (again, see Komodo) and assigning icons makes it easy to find the right ones more quickly.

+ design view
+ mongo shell integration
+ mongod log tailing

Create or find a plugin that supports Gradle natively like Subclipse does for Subversion. IntelliJ supports this now natively and I believe it's becoming a large market.

Add Struts like editing support and templating support on Controller, View/ViewModel, and Data Models as Ember is using Convention over Configuration, MyEclipse can seamlessly help user to manage that. In addition add context sensitive like interllisense to the editor. An integrated compiler would also help in large system development.

Its a hugely unproductive task to create Java beans from JSON/XML files. Having a utility to reverse engineer beans and adding jaxb annotations will save lot of time for everyone.