Bug 771695

Summary: JON 2.4.2 Release Candidate #2 ... CLI .jars not signed
Product: [Other] RHQ Project Reporter: Mike Foley <mfoley>
Component: AgentAssignee: Simeon Pinder <spinder>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: hrupp, spinder
Target Milestone: ---   
Target Release: JON 2.4.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-04 20:47:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
jar file none

Description Mike Foley 2012-01-04 16:37:27 UTC
Created attachment 550723 [details]
jar file

Description of problem:  JON 2.4.2 Release Candidate #2 ... CLI .jars not signed


Version-Release number of selected component (if applicable):  JON 2.4.2 


How reproducible:
100%

Steps to Reproduce:
1.  open rhq-remoting-client-api-3.0.1.JON242.GA.jar
2.  META-INF directory does not show .jar signing files


Attachment:  rhq-remoting-client-api-3.0.1.JON242.GA.jar

Comment 1 Simeon Pinder 2012-01-04 19:52:29 UTC
This is by design. The JON 2.4.1 CLI was unusable because of signing issues. See https://bugzilla.redhat.com/show_bug.cgi?id=685003 for more details. 

As JON 2.4.2.GA is meant to be a cumulative fix release for 2.4.1, as described by BZ 685003, the problematic signed jars have been unsigned.

I'm moving this to ON_QA.  Basically this is already verified as per the bug report.  Additionally we should make sure that the signing issues reported no longer occur and that the CLI is indeed usable with this fix.