Bug 1011591
Summary: | Manual patch instructions and contents inaccurate | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Marek Winkler <mwinkler> |
Component: | Patch Process | Assignee: | nwallace <nwallace> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | BRMS 5.3.1 | ||
Target Milestone: | GA | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 986451 | ||
Attachments: |
Description
Marek Winkler
2013-09-24 15:12:18 UTC
I have investigated the jar differences in detail: drools-compiler-5.3.1.BRMS-P04.jar - the only difference is timestamps, which is not an issue drools-core-5.3.1.BRMS-P04.jar, jbpm-flow-5.3.1.BRMS-P04.jar - these two jars differ from their counterparts not only in timestamps, but some classes they contain are actually different commons-httpclient.jar - one class is different when comparing with its counterparts in $REST_HOME/lib/ and $SEAM_HOME/lib I can attach diff output, if needed. Created attachment 802635 [details]
backup.sh - script used for testing manual patch instructions
Created attachment 802636 [details]
remove.sh - script used for testing manual patch instructions
Created attachment 802637 [details]
patch.sh - script used for testing manual patch instructions
In case you could use some (really basic) scripts for testing manual patch instructions, I have attached 3 scripts that I used to verify patching of standalone distribution. Please update the variables defining file locations in each script first. The scripts are run in the following order against BRMS 5.3.1 GA standalone: - backup.sh - copies original versions of jars being patched from the standalone distribution into a directory specified in the script - remove.sh - deletes the old versions of jars being patched from the standalone distribution - patch.sh - copies patched jars into the standalone distribution The scripts should not print any warnings. I have found another problem with manual patch: BZ986451/business-central-server-ee6.war/WEB-INF/lib does not contain the following jars (while BZ986451/business-central-server.war/WEB-INF/lib contains them): - drools-core-5.3.1.BRMS-P04.jar - jbpm-flow-5.3.1.BRMS-P04.jar - jbpm-flow-builder-5.3.1.BRMS-P04.jar - jbpm-gwt-core-5.3.1.BRMS-P04.jar - jbpm-gwt-form-5.3.1.BRMS-P04.jar - jbpm-human-task-5.3.1.BRMS-P04.jar Ok, jars are in BZ986451/business-central-server-ee6.war/WEB-INF/lib now. After sorting out a few additional inaccuracies patch instructions, I have verified that the patch instructions are now correct, and manually patching 5.3.1.GA leads to a binary equivalent to the one distributed in the 5.3.1-P04 patch. |