Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 962138

Summary: JBDS detects SOA 6 as version 7.2
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Martin Vecera <mvecera>
Component: ToolingAssignee: Rob Cernich <rcernich>
Status: CLOSED CURRENTRELEASE QA Contact: Len DiMaggio <ldimaggi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0.0, 6.0.0 GACC: apodhrad, atangrin, dlesage, kconner, mvecera, soa-p-jira
Target Milestone: ---Flags: mvecera: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-22 06:49:17 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:
Attachments:
Description Flags
How it looks in JBDS 7.1.0.GA none

Description Martin Vecera 2013-05-11 22:39:10 UTC 
When JBDS 6.0.1 is about to add SOA 6 server runtime, it shows that the server has version 7.2. EAP 6.1 Beta is correctly detected as 6.1 but once I unzip SOA 6 over it, JBDS recognizes it as 7.2.
Comment 7 Andrej Podhradsky 2014-01-29 14:14:17 UTC 
Created attachment 857092 [details]
How it looks in JBDS 7.1.0.GA
Comment 9 Rob Cernich 2014-10-21 19:33:21 UTC 
Is this still an issue?  The attached screenshot looks correct and JBDS 7.x is the latest release, with 8.0 expected shortly.  If so, can we close this as out of date?
Comment 10 Andrej Podhradsky 2014-10-22 06:49:17 UTC 
This is fixed in current releases (JBDS 7.1.1.GA and also JBDS 8.0.0.GA)