Bugzilla – Full Text Bug Listing
| Summary: | m2e project configurators don't run in a defined order | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | benson margulies <bimargulies> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | fbricon, gregory.amerson, igor |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 449495 | ||
| Bug Blocks: | |||
org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.putSetupMojoExecution(MojoExecutionKey, MojoExecution) creates a HashMap, not a LinkedHashMap, so the order is unpredictable, which might be relevant. org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.putSetupMojoExecution(MojoExecutionKey, MojoExecution) creates a HashMap, not a LinkedHashMap, so the order is unpredictable, which might be relevant. I may have a clue, but I don't know what to do about the clue. I suspect that, from a lifecycle standpoint, PMD runs first. But from a configuration standpoint, PMD has to run *last*. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Thank for the reminder, Genie, but this is one of the long-term problems we'll need to address eventually, I'll take it from here. You can now replace secondaryTo with runsAfter="org.eclipse.m2e.jdt.javaConfigurator?" Note the ? (==optional) is necessary because org.eclipse.m2e.jdt.javaConfigurator is bound to a different mojo execution than checkstyle/pmd. See bug #449495 *** This bug has been marked as a duplicate of bug 449495 *** |
Build Identifier: 20110602-0820 While debugging, I am stopped at {com.basistech.m2e.code.quality.checkstyleConfigurator=com.basistech.m2e.code.quality.checkstyleConfigurator:M2Eclipse maven-checkstyle-plugin project configurator, com.basistech.m2e.code.quality.pmd=com.basistech.m2e.code.quality.pmd:M2E-PMD, org.eclipse.m2e.jdt.javaConfigurator=org.eclipse.m2e.jdt.javaConfigurator:JDT}. The configurators come back in the following order: {com.basistech.m2e.code.quality.checkstyleConfigurator=com.basistech.m2e.code.quality.checkstyleConfigurator:M2Eclipse maven-checkstyle-plugin project configurator, com.basistech.m2e.code.quality.pmd=com.basistech.m2e.code.quality.pmd:M2E-PMD, org.eclipse.m2e.jdt.javaConfigurator=org.eclipse.m2e.jdt.javaConfigurator:JDT} This can't work, since JDT needs to run first. I can't seem to discover any way to influence the order. I don't yet understand how to get into this state where the order looks like this. Reproducible: Always