Bug 771695 - JON 2.4.2 Release Candidate #2 ... CLI .jars not signed
Summary: JON 2.4.2 Release Candidate #2 ... CLI .jars not signed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: ---
: JON 2.4.2
Assignee: Simeon Pinder
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-04 16:37 UTC by Mike Foley
Modified: 2012-01-04 20:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-04 20:47:41 UTC

Attachments (Terms of Use)
jar file (14.76 KB, application/java-archive)
2012-01-04 16:37 UTC, Mike Foley 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 685003 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 685003

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.
Note You need to log in before you can comment on or make changes to this bug.