Bug 778665 (SOA-1138) - Wrong ESB runtime number in file: jboss-soa-p.4.3.0/jboss-as/server/default/deploy/jbossesb.sar/lib/jbossesb-rosetta.jar/VERSION
Summary: Wrong ESB runtime number in file: jboss-soa-p.4.3.0/jboss-as/server/default/...
Keywords:
Status: CLOSED DUPLICATE of bug 2040112
Alias: SOA-1138
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 CP01
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-20 09:06 UTC by Denny Xu
Modified: 2009-01-20 11:14 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-20 11:14:54 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1138 0 None None None Never

Description Denny Xu 2009-01-20 09:06:51 UTC 
Date of First Response: 2009-01-20 05:22:54
project_key: SOA

I try to get the version number of ESB runtime that  jboss-soa-p.4.3.0 contained,  but when I open the file: jboss-soa-p.4.3.0/jboss-as/server/default/deploy/jbossesb.sar/lib/jbossesb-rosetta.jar/VERSION
the displayed version number is 4.3, since the SOA-P 4.3 contains ESB 4.4, so it is a bug.
Comment 1 Max Rydahl Andersen 2009-01-20 10:22:54 UTC 
Kevin - could you comment on this ? 

Looking at MANIFEST.MF it also list 4.3 instead of 4.4 for ESB jar making it impossible for both support, users and tooling to identify what runtime is actually being used here. If it really want to be different from org.jboss.esb 4.4 then it should also use different package/configuration/url names.
Comment 2 Kevin Conner 2009-01-20 10:27:36 UTC 
The version number represents the SOA version and not the ESB project version.  This is set by the SOA platform build and not ESB.
Comment 3 Mark Little 2009-01-20 11:13:51 UTC 
Link: Added: This issue is incorporated by SOA-1116
Note You need to log in before you can comment on or make changes to this bug.