Bug 724316 (BRMS-261) - Need a manifest file for GA build
Summary: Need a manifest file for GA build
Keywords:
Status: CLOSED NOTABUG
Alias: BRMS-261
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Release Process
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: CR1
: BRMS 5.2.0.GA
Assignee: Ryan Zhang
QA Contact: Lukáš Petrovický
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-08 15:29 UTC by Len DiMaggio
Modified: 2011-10-05 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
<!-- A signed manifest file is included in the BRMS-standalone-5.2.0.zip file. Use this to check the integrity the JARs on a per-file basis. (I'll remove the comment tags when this has moved from ON-QA)-->
Clone Of:
Environment:
Last Closed: 2011-09-30 12:52:05 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779575 0 urgent CLOSED Need a manifest file for GA build 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker BRMS-261 0 None Closed Need a manifest file for GA build 2012-03-01 00:40:41 UTC
Red Hat Issue Tracker soa-3196 0 None Closed Extra META-INF directory in soa .zip for 5.2 ER1 build 2012-03-01 00:40:42 UTC

Internal Links: 779575

Description Len DiMaggio 2010-03-08 15:29:07 UTC 
securitylevel_name: Public

See SOA-1950 for context - we will need the same type of "trusted manifest" for BRMS 5.0.2
Comment 1 Len DiMaggio 2010-03-08 15:29:29 UTC 
Link: Added: This issue is related to SOA-1950
Comment 2 Dana Mison 2010-10-27 03:05:59 UTC 
Release Notes Text: Added: test
Comment 3 Dana Mison 2010-10-27 03:13:48 UTC 
Release Notes Text: Removed: test
Comment 4 David Le Sage 2010-11-03 05:02:33 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: dlesage
Comment 5 David Le Sage 2010-12-08 05:30:48 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: BRMS-261

A signed manifest file is now included in the soa-5.0.0.zip file. Use this to check the integrity the JARs on a per-file basis.
Comment 6 David Le Sage 2010-12-08 05:31:06 UTC 
Labels: Removed: rn-dlesage rn-open Added: rn-dlesage rn-done-resolved
Comment 7 Anne-Louise Tangring 2011-09-13 17:58:51 UTC 
This should now be part of the build process. Re-test to verify.
Comment 8 lcarlon 2011-09-22 23:56:06 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
<!-- A signed manifest file is included in the BRMS-standalone-5.2.0.zip file. Use this to check the integrity the JARs on a per-file basis. (I'll remove the comment tags when this has moved from ON-QA)-->
Comment 9 Lukáš Petrovický 2011-09-30 09:47:52 UTC 
This file is not present in BRMS 5.2.0 ER5 Standalone.
Comment 10 Ryan Zhang 2011-09-30 11:11:33 UTC 
MEAD was able to produce those MANIFEST file. 
But it has changed since https://issues.jboss.org/browse/SOA-3196

Need to sync up with Len.
Comment 11 Lukáš Petrovický 2011-09-30 11:17:39 UTC 
Len(In reply to comment #10)
> MEAD was able to produce those MANIFEST file. 
> But it has changed since https://issues.jboss.org/browse/SOA-3196
> 
> Need to sync up with Len.

Len, please decide - it's either SOA-3196 or this. Not both.
Comment 13 Lukáš Petrovický 2011-09-30 12:52:05 UTC 
We decided not to resolve this. SOA-3196 takes precedence.
Note You need to log in before you can comment on or make changes to this bug.