<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="https://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Single Installation Patching
</h3>
<span style="margin-bottom: 10px;">
new comment by <a href="https://community.jboss.org/people/brian.stansberry">Brian Stansberry</a> <a href="https://community.jboss.org/docs/DOC-47500#comment-11204">View all comments on this document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><blockquote class="jive-quote"><p>Jeff Mesnil wrote:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>
                        <p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><div class="jive-rendered-content"><p>I have been working on the patch CLI command to patch an AS7 installation and add to tweak the code related to module to be able to generate a correct patch generated by diffing 2 AS7 installations.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>When comparing modules to check whether they have been updated, computing the dir's checksum is not correct:</p><p>* Jar files generated during AS7 build can not have the same checksum since the creation date of the class files is store in the jar's zip entries.</p><p>=> this concerns AS7's own modules (org/jboss/as/...) and also jandex jars for 3rd party libraries</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>To circumvent that, instead of computing the SHA-1 of the jar files, I compute the checksum of the file's zip entries name/size/crc (ie I exclude the date metadata).</p><p>I also need to exclude some entries from the jar:</p><p>* Some java sources are generated at build time (logger and bundle classes) and embed their generation date into the code => the .class files have different size and crc</p><p>* META-INF/MANIFEST.MF and pom.properties files also contains the jar creation date => these files have different size and crc</p></div><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>
                    </blockquote><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>When I replied to this before, I fear I came off more negative about it than I intended.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I don't think it's the right thing to do when generating a cumulative patch.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I'm not sure if it's the right thing to do with no way to turn it off when generating a one-off patch. But I can certainly imagine people preparing those would find it very useful to have a configurable option to do a generate-by-diff patch instead of a specified-content patch without having these kinds of date issues leading to irrelevant stuff ending up in the patch.</p></div>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>