[jboss-dev] Update to jboss-cl-2.2.x stable release

[Ales Justin]

Afair, the trunk and current 2.0.x branch also include some lifecycle, 
shutdown changes made by Adrian.
This is all thoroughly tested, but afaik, not (fully) needed for our OSGi.

I'm saying fully, as we can still use jb-cl, w/o "shutdown" changes,
it's just that we won't be completely OSGi compatible - diff undeploy 
behavior.

I'm not aware of any change that would break backwards compatibility.
The stuff Adrian and Thomas added just adds new features, backed by 
default behavior in abstract/common classes.

So, I'm OK with any option we choose:
* release 2.2.0.Alpha1
* release 2.0.9.GA
* release 2.0.8.SP1 with just Thomas' needed changes

Dimitris Andreadis wrote:
> Can we have someone from MC please review the needed changes to have a second opinion 
> regarding backwards compatibility?
> 
> As Brian pointed out, we should try to stick to the M2 schedule (which has been known for 
> some time now) without adding unnecessary risk.
> 
> Thomas Diesler wrote:
>> OSGi related changes to the CL 2.0.8 code base are about the OSGi notion 
>> of fragments and native code.
>> Existing classloading semantics would not be affected AFAIK.
>>
>> -thomas 
>>
>> On 01/26/2010 10:24 AM, Thomas Diesler wrote:
>>> This means, that M2 would be the first AS release since the 
>>> interception of JBoss OSGi in Mar-2009 that will NOT have support for 
>>> our own JBossMC based OSGi Core Framework.
>>>
>>> Which would not be in line with what Mark says here:
>>>
>>> http://www.serverwatch.com/news/article.php/3860401/Red-Hats-JBoss-Aims-to-Improve-User-Productivity-UI-in-2010.htm
>>>
>>>     "We can support OSGi bundles running alongside our native
>>>     equivalent format," Little said. 
>>>
>>> Instead, I'd suggest we do the necessary jboss-cl update and the QA 
>>> associated with it.
>>> In case jboss-cl 2.2.x is not in a state where it can be released and 
>>> brought into AS, I could also try to merge the necessary changes back 
>>> to the 2.0.8 code base
>>> and we include the resulting 2.0.8.SP1 release.
>>>
>>> Whatever the direction is, I believe an update is necessary (i.e. 
>>> JBAS-7650 is not optional). If you want to go the 2.0.8 route, please 
>>> let me know and I can do the necessary merges and possibly the SP1 
>>> release if Adrian is not available.
>>>
>>> cheers
>>> -thomas
>>>
>>>
>>> On 01/25/2010 05:32 PM, Brian Stansberry wrote:
>>>> There'd have to be a release first; looking at the task list[1] it seems 
>>>> we're a ways away from an 2.2.0.Alpha.
>>>>
>>>> The integration cutoff for M2 is Jan 31, and for something as 
>>>> fundamental as this it would really have to be done (including full AS 
>>>> testsuite runs done before commit showing no regressions) by tomorrow. I 
>>>> don't think that's likely, so IMO this is an M3 upgrade.
>>>>
>>>> [1] 
>>>> https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310570&fixfor=12313375
>>>>
>>>> On 01/25/2010 01:54 AM, Thomas Diesler wrote:
>>>>   
>>>>> Hi Folks,
>>>>>
>>>>> https://jira.jboss.org/jira/browse/JBAS-7650
>>>>>
>>>>> is there an update of jboss-cl planned in the future? What's preventing
>>>>> AS from using jboss-cl 2.2.x?
>>>>>
>>>>> cheers
>>>>> -thomas
>>>>>
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>> Thomas Diesler
>>>>> JBoss OSGi Lead
>>>>> JBoss, a division of Red Hat
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>     
>>>>   
>>> -- 
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>> Thomas Diesler
>>> JBoss OSGi Lead
>>> JBoss, a division of Red Hat
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> -- 
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thomas Diesler
>> JBoss OSGi Lead
>> JBoss, a division of Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>