[MINSTALL-115] Setting installAtEnd causes no installs to occur when a multimodule project has multiple class realms

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: 3.0.0
• Component/s: install:install
• Assignee: Tamas Cservenak
• Reporter: Philip Pearson
• Created: 10/Aug/15 17:56
• Updated: 22/Oct/22 10:30
• Resolved: 03/Jul/22 18:37

Description

When the installAtEnd configuration parameter is set to true on a multimodule project with multiple class realms then because a different class loaders creates instances of the InstallMojo class there will be muliple instances of readyProjectsCounter and installRequests.

However, because the end is determined by projectsReady = readyProjectsCounter.incrementAndGet() == reactorProjects.size() it will never complete as readyProjectsCounter will never equal the size reactorProjects if even one project is executed in another class realm.

maven-deploy-plugin partially solved this in MDEPLOY-193 by using project.equals(reactorProjects.get(reactorProjects.size() - 1)) instead. However, the installation is a little more complex than the deploy as we need to read the used the createChecksum and updateReleaseInfo configuration parameters from each installed project - we can't store them ahead of time because of the issue with the class realms, so we need to read the plugin configurations before we can call installProject(instalRequest).

Issue Links

• is required by: KYLIN-3644 NumberFormatExcetion on null values when building cube with Spark
• relates to: MINSTALL-102 installAtEnd does not install artifacts for multi-module with packaging maven-archetype
• links to: GitHub Pull Request #1
• links to: GitHub Pull Request #15