Bug 1011106 - version.txt needs to be updated during installation
Summary: version.txt needs to be updated during installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: ---
Assignee: Miles Tjandrawidjaja
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 15:54 UTC by Len DiMaggio
Modified: 2014-09-03 04:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Len DiMaggio 2013-09-23 15:54:31 UTC
Description of problem:

In ER3, version.txt contains:
   JBoss Enterprise Application Platform - Version 6.1.0.GA

We should change this to:
   Red Hat JBoss Fuse Service Works - Version 6.0.0

(Can we also append "beta,", "GA," etc.?

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anne-Louise Tangring 2013-09-24 17:15:33 UTC
Append to version.txt rather than replace.

Comment 3 Nick Cross 2013-09-25 15:50:38 UTC
After discussion with Alan we will use the existing version from the manifest e.g. 6.0.0.ER3-redhat-1 without appending any further information.

Comment 4 Miles Tjandrawidjaja 2013-09-26 19:26:51 UTC
The version.txt file should now contain the proper information based from manifest.
Ex. Red Hat JBoss Fuse Service Works - Version 6.0.0.ER3-redhat-1

http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=7e57e6516a5c56b159189791af02fa97210eb408

Comment 5 Len DiMaggio 2013-10-04 19:51:47 UTC
Verified in the Oct 4 ER4 respin #2 build.

Text reads:

=========================
JBoss Enterprise Application Platform - Version 6.1.0.GA

Red Hat JBoss Fuse Service Works - Version 6.0.0.ER4-redhat-1
=========================


Note You need to log in before you can comment on or make changes to this bug.