Bug 471038 – Configurator is not called if secondary for a goal, but also primary for another goal
m2e 1.6 introduced runsAfter and runsBefore directive to specify configurator run order. Also, the concept of primary and secondary configurators are still here, where the primary configurator runs first, then the secondaries later. In a corner case when a configurator is secondary for an execution, but primary for another exececution, the mapping calculator algoritm is incorrect and does not adds this configurator. For example the m2e-android plugin defines runsAfter to the java configurator, but it also maps Android plugin goals which are of course not mapped by the java configurator. This way m2e-android is a secondary configurator to the java one, but primary as the configurator to Android goals. The current algorithm fails to add m2e-android. |
Read full article from Bug 471038 – Configurator is not called if secondary for a goal, but also primary for another goal
No comments:
Post a Comment