[CONTINUUM-1915] Continuum 1.2 does not build the project when it has changes in sub-modules and the m2 build is recursive

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.2.3
• Component/s: Integration - Maven 2
• Environment: Linux
• Flags: Patch
• Assignee: Olivier Lamy
• Reporter: apache maillist
• Created: 01/Oct/08 20:27
• Updated: 05/Apr/15 14:44
• Resolved: 03/Dec/08 17:10

Description

Log shows:
2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building

In continuum, the working copy looks like this

• parent-md
• mycommon
• myintegration
• mybusiness
• mydo
• pom.xml

the pom.xml is used for adding project into continuum

the pom.xml consist of those projects

<modules>
<module>parent-md</module>
<module>mycommon</module>
<module>myintegration</module>
<module>mybusiness</module>
<module>mydo</module>
</modules>

parent-md is the parentpom for all project listed

After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.

Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.

Issue Links

• is related to: CONTINUUM-2108 Continuum 1.2 does not build the project when it has changes in sub-modules and the m2 build is recursive (reopen)
• is related to: CONTINUUM-1807 Improve performance on maven2 builds by building a pom project if changes are only in sub-modules

Sub-Tasks

• sub-modules bug still exists: Closed