[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14323: --------------------------------------------- For those who don't know or remember the big performance boost from old m2e to new m2e is that it does *not* automatically run the "update project configuration" since it has sideeffects which in common cases can cause recursive triggering of "update project configuration". Thus it is not automatically done since it had bad sideeffects. That said I think there are two things that could be done here: A) open a RFE against m2e to atleast make "Update project configuration" a command so it can be hotkey bindable AND at least possible to show up in Cmd+3 (quick access) B) Look into if one could not detect via the pom hiearchy to run an "update project configuration" when something that is a parent pom gets updated - run that update project configuration and have a "lock" to prevent it from triggering again automatically. It would be a "poor man" version of what was there in the past but if a user can invoke this across multiple projects then the IDE should be able to do it too without causing havoc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira