|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Code changed in jenkins
User: Stephen Connolly
Path:
core/src/main/java/hudson/model/Job.java
http://jenkins-ci.org/commit/jenkins/503c3bd2e6f2ec85514e16a260396ddae68f03ae
Log:
[FIXES JENKINS-2494] Restore correct behaviour
This route seems slightly less fragile, though people could still add ItemListeners
with order == -Double.MAX_VALUE which would then introduce intdeterminism.
A marker interface would remove that indeterminism as the onCopyComplete method would
be only called on the Job as the last method... but it could be hard to
ensure that all ItemGroupMixin's respect the calling of onCopyComplete contract
hence this approach seems better to me for that reason