Damien Lecan a écrit :
ok, with two build def, it was easy to reproduce it :)
Ouf, I'm pleased to read that :-)
I know :)
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.
It is what I suspected. Thanks to testing again
np
unfortunately, I don't think we can't fix it for 1.1.
As you want, but I think this is a major issue. If it's not possible
for 1.1, I hope it will be for 1.1.1 !
Did you fill in a jira request to track this ?
I'll let you file the issue.
Emmanuel
