[MNG-4357] [regression] Custom packagings from build extensions are not reliably loaded during a reactor build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Plugins and Lifecycle, Reactor and Workspace
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 14/Sep/09 08:12
• Updated: 14/Sep/09 12:31
• Resolved: 14/Sep/09 12:31

Description

Building XWiki platform with trunk in one go produces

[ERROR] Unknown packaging: maven-archetype @ org.xwiki.platform.tools:xwiki-archetype-macro:1.1-SNAPSHOT

The mentioned project properly declares the required build extensions in its POM and builds fine in isolation.

The issue boils down to the active component map DefaultLifecycleExecutor.lifecycleMappings not being properly updated when switching the projects in the reactor. In detail, AbstractComponentCollection.checkUpdate() from Plexus doesn't update the map if the number of component descriptors hasn't changed. This apparently misses the situation where the total count of component descriptors from two different class realms is the same but the set of role hints has changed, e.g. [one, two] vs. [one, three].