[jboss-dev] AS 5.1 and JBoss Messaging 2

[Tim Fox]

Resending

Tim Fox wrote:
> Jason T. Greene wrote:
>> I really wish we could. Tim said theres pretty much no was JBM2 can 
>> make Beta1, but it could make CR1. The question is, would it be 
>> stable and TCK compliant enough that it doesn't end up delaying GA?
> No, JBM 2.0 is a major release and is not compatible with JBM 1.4. 
> That's why we can't replace JBM 1.4 in a minor release since AS minor 
> versions need to be compatible, and why it's being offered as a 
> technology preview, not replacement for default JMS provider.
>>
>> Dimitris Andreadis wrote:
>>> Why not keep it simple and ship JBM2 in AS 5.1 Beta/CR? I suppose 
>>> it's a matter of dates, right?
>>>
>>> Jason T. Greene wrote:
>>>> Because that is just configuration. Shipping just 1.4 in the 
>>>> community, and 1.4 and 2.0 in EAP is completely backwards from the 
>>>> whole upstream concept.
>>>>
>>>> David Ward wrote:
>>>>> Why would this be weird?  .com/EAP 4.x has a "production" profile 
>>>>> that .org/AS 4.x does not...
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>> Jason T. Greene wrote:
>>>>>> Part of the problem is that EAP is planning on including a JBM2 
>>>>>> profile / option. IMO it would be very weird to ship something in 
>>>>>> EAP but not in AS. Besides creating a profile, another option we 
>>>>>> have is to include JBM2 with an install script in docs/examples. 
>>>>>> Then someone could switch any AS profile to JBM2.
>>>>>>
>>>>>> Dimitris Andreadis wrote:
>>>>>>> We have enough configurations so far, so I don't think it's a 
>>>>>>> good idea adding any new ones until we come up with with a way 
>>>>>>> to share most of the jars/configuration.
>>>>>>>
>>>>>>> In your case it's better to offer the preview as a separate 
>>>>>>> download.
>>>>>>>
>>>>>>> Andy Taylor wrote:
>>>>>>>> As part of the AS 5.1 release we will be shipping JBM 2.0 as a 
>>>>>>>> technology preview. This will require 1 or more new profiles to 
>>>>>>>> be created. I have created a branch (Branch_5_x_JBM2) to use 
>>>>>>>> for now which i will merge in once JBM 2.0 is released and 
>>>>>>>> there is something concrete and working.
>>>>>>>>
>>>>>>>> What new profiles we need to add is open to discussion. We'll 
>>>>>>>> definitely need a copy of default as a start which could be 
>>>>>>>> called messaging-2. However, from a JBM2 point of view, it 
>>>>>>>> would be good to also demonstrate clustering which would mean a 
>>>>>>>> copy of all, say messaging-2-all, and since JBM2 can run with a 
>>>>>>>> minimal set of services maybe a messaging-2-minimal as well.
>>>>>>>>
>>>>>>>> I appreciate that adding all 3 might be too many new profiles 
>>>>>>>> to add so I'd like to hear peoples views!
>>>>>>>>
>>>>>>>> Andy Taylor Core Developer
>>>>>>>> JBoss Messaging
>>>>>>>> _______________________________________________
>>>>>>>> jboss-development mailing list
>>>>>>>> jboss-development at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>> _______________________________________________
>>>>>>> jboss-development mailing list
>>>>>>> jboss-development at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>>
>>
>>
>
>


-- 
Tim Fox
Messaging Lead
JBoss - a division of Red Hat

http://jbossfox.blogspot.com/

irc.freenode.net#jbossmessaging

fox at redhat.com