Bug 777540 (SOA-41) - Oct 1 SOA standalone Platform build includes JBoss Messagaging 1.3 - should be 1.4
Summary: Oct 1 SOA standalone Platform build includes JBoss Messagaging 1.3 - should b...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-41
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: 4.2 IR2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 IR4
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA-41
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-06 02:24 UTC by Len DiMaggio
Modified: 2007-10-31 14:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
soa-standalone.zip (sept 25 2007) RHEL5 java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
Last Closed: 2007-10-31 14:19:05 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-41 0 None None None Never

Description Len DiMaggio 2007-10-06 02:24:14 UTC 
Date of First Response: 2007-10-06 03:12:33
project_key: SOA

The Oct 1 standalone ESB spin includes:

server/default/lib/boss-messaging.jar - size = 1024199

VERSION file = 

#
# This is an automatically generated file. DO NOT EDIT!
#
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.3.0.GA
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=3
jboss.messaging.providerIncrementingVersion=15


The Oct 1 SOA/embedded with AS includes:

jboss-as/server/all/lib/jboss-messaging.jar - size = 1032793

VERSION file = 

#
# This is an automatically generated file. DO NOT EDIT!
#
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.4.0.CR1
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=4
jboss.messaging.providerIncrementingVersion=16
Comment 2 Tim Fox 2007-10-06 07:12:33 UTC 
Another issue, is the SOA AS build is using 1.4.0.CR1 - it should be using 1.4.0.GA - 1.4.0.CR1 is *old*!

Suggestion: Create a process whereby you make sure you're using all the correct/latest versions of the components before creating the build.
Comment 3 Tim Fox 2007-10-06 07:14:11 UTC 
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingReleaseHistory
Comment 4 Len DiMaggio 2007-10-07 02:14:01 UTC 
Link: Added: This issue is a dependency of JBQA-1002
Comment 5 Kevin Conner 2007-10-08 14:39:50 UTC 
The current ESB build uses 1.3.0GA and we are shortly moving up to 1.4.0.GA

There is one question that needs to be answered before we do this, we need to know which version of JBoss Remoting will be used in the EAP so that we can upgrade this at the same time.

JBoss Messaging references JBR 2.2.2.SP1-brew, which I believe is equivalent to 2.2.2.SP1 except it has been compiled with JDK5.  Ron says that there is another issue (JBREM-811) which needs to be fixed and that it is currently available via 2.2.2.SP1.patch01-brew.
Comment 6 trev 2007-10-31 14:18:33 UTC 
from the esb IR2 build
server/default/lib/boss-messaging.jar - size 1057500

# This is an automatically generated file. DO NOT EDIT!
#
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.4.0.GA
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=4
jboss.messaging.providerIncrementingVersion=18
Note You need to log in before you can comment on or make changes to this bug.