[ https://issues.jboss.org/browse/JBDS-3999?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-3999 at 8/15/16 4:59 AM: ------------------------------------------------------------ A wild problem has appeared! Neither the file name nor the sha for jdk is updated, which means it still downloads as jdk.zip and checks against the old sha. There are 2 possible outcomes of this situation: - an existing cached jdk.zip is used during the build, because the sha is the same - results in installation failure (calling msiexec on a zip archive) - the msi file is downloaded (if no jdk.zip is cached) and then the build fails because the sha doesn't match So far it seems we've been 'lucky' enough to only get the first option on CI builds so it nicely concealed the error. was (Author: jrichter1): A wild problem has appeared! Neither the file name nor the sha for jdk is updated, which means it still downloads as jdk.zip and checks against the old sha. There are 2 possible outcomes of this situation: - an existing cached jdk.zip is used during the build, because the sha is the same - results in installation failure (calling msiexec on a zip archive) - the msi file is downloaded (if no jdk.zip is cached) and then the build fails because the sha doesn't match -- This message was sent by Atlassian JIRA (v6.4.11#64026)