|
Sort Order:
I took a look at the projects causing the ".. is duplicated in the reactor" in vmbuild and it seems the Sling projects were added twice in the group? As for the jUDDi project, there are two groups of the project added in vmBuild.. both the projects in the two groups are similar and that's what's probably causing the "..is duplicated" warning message. The warning "...duplicated in the reactor" is displayed when a project is added twice (either in different groups or the same group). Given this scenario, the scheduled build is triggered but the project scm and the projects are not updated and queued for build. I believe this was fixed by |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Critical
Scheduled builds stopped after upgrade
looking at the logs from https://issues.apache.org/jira/browse/INFRA-2037
, the warn message will only appear if continuum is trying to build more than one instance of the same project, with the same groupId, artifactId, version.