#Jrebel maven plugin configuration full#
#Jrebel maven plugin configuration series#

(execution: generate-sources-input, phase: generate-sources) Plugin execution not covered by lifecycle configuration: m2e will create error marker like below for all plugin executions that do not have lifecycle mapping in any of the mapping metadata sources. We call these “lifecycle mapping metadata sources”. Project build lifecycle mapping can be configured in a project’s pom.xml, contributed by Eclipse plugins, or defaulted to the commonly used Maven plugins shipped with m2e. We call these instructions “project build lifecycle mapping” or simply “lifecycle mapping” because they define how m2e maps information from project pom.xml file to Eclipse workspace project configuration and behaviour during Eclipse workspace build. To solve these long-standing issues, M2Eclipse 1.0 requires explicit instructions what to do with all Maven plugins bound to “interesting” phases (see (M2E interesting lifecycle phases “wikilink”)) of a project build lifecycle. Various JVM and OS resources leaks by Maven plugins was another common cause of problems. And in some cases workspace build would go on forever. In some cases, generated/filtered resources would go missing. In some cases projects appeared to work fine. Out-of-workspace resource changes made by Maven plugin triggered unexpected workspace builds. Most, if not all, such problems were traced back to one of two root causes. For example MNGECLIPSE-823 was the most voted issue in M2Eclipse jira and it was a direct manifestation of this “flakiness”.

#Jrebel maven plugin configuration series#

Probably even worse, it did not always work for many projects, so we had to go through series of refresh/update dependencies/update configuration/rebuild voodoo (or “m2eclipse dance” as some called it) to get projects in a good state. Unfortunately, this did not work well or not at all for many projects. On top of that, there was project-level setting to “skip” maven-compiler-plugin execution. Some of these goals were configured at workspace level, some in project/.settings.

#Jrebel maven plugin configuration full#

This was controlled by many different sets of maven goals – goals when projects were imported,a project configuration changes and workspace full and incremental builds. M2Eclipse 0.12 and earlier executed some parts of Maven build lifecycle inside Eclipse and then configured the Eclipse project based on after-execution state collected in MavenProject.