[ http://jira.codehaus.org/browse/CONTINUUM-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated CONTINUUM-1507: ---------------------------------------- Fix Version/s: To Sort > Build are always done when it exists several build definitions for the same > project group > ----------------------------------------------------------------------------------------- > > Key: CONTINUUM-1507 > URL: http://jira.codehaus.org/browse/CONTINUUM-1507 > Project: Continuum > Issue Type: Bug > Affects Versions: 1.1-beta-2, 1.1-beta-3 > Reporter: Damien Lecan > Priority: Critical > Fix For: To Sort > > > Based on this discussion > http://www.nabble.com/When-builds-are-done-in-multi-module-projects---tf4508232.html > Continuum doesn't handle correctly previous build results when several build > definitions are enabled for the same project group. > As Emmanuel said : > After to check scm changes, Continuum look at dependencies changes. To do > that, it look only at dependencies that are continuum project too. For them, > a new version is detected if the latest build result of the > dependency/project is more recent than the latest build result of the current > build definition. In case on more than one build def, we can't know if all > build def of the dependency generate an artifact or not, we know only if a > new build was done and we add it in dependencies changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira