Bug 1209192

Summary: [GSS](6.4.z) Fix corrupt Manifest in H2 jar
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rick Wagner <rwagner>
Component: BuildAssignee: Vladimir Dosoudil <dosoudil>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bbaranow, bmaxwell, cdewolf, jawilson, mweiler, pmackay, psotirop, vtunka
Target Milestone: CR1   
Target Release: EAP 6.4.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:35:37 UTC 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: 1279553    

Description Rick Wagner 2015-04-06 16:18:06 UTC
Description of problem:  Though the H2 database is unsupported, some customers still make use of it.  (We provide a productised version with EAP).  

The current version of the H2 jar contains a corrupted Manifest file in the META-INF directory.  The Manifest contains the following line:
"MANIFEST.MF: "Main-Class: org.h2.tools.Console^M""

The '^M' at the end of the line prevents the customer from starting the jar as a Java Main.

Please correct this problem.

Comment 12 Mike McCune 2016-03-28 22:30:10 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 14 Peter Mackay 2016-05-05 11:57:49 UTC
Verified with EAP 6.4.8.CP.CR2

Comment 15 Petr Penicka 2017-01-17 12:35:37 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.