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

Brian Stansberry brian.stansberry at redhat.com
Wed Jan 27 10:20:14 EST 2010


Ok, thanks. I knew you did a lot of testing in the JBoss OSGi but forgot 
OSGi wasn't bundled in the AS dist yet.

On 01/27/2010 04:41 AM, Thomas Diesler wrote:
> OSGi is functionality that is currently not shipped as part of the AS.
>
> Here is the issue that covers this
> https://jira.jboss.org/jira/browse/JBAS-7661
>
> To get an idea about the level of coverage I do, have a look at
> http://jbmuc.dyndns.org/jboss-osgi/userguide/html/ChapGettingStarted.html#SecHudson
>
>
>
> cheers
> -thomas
>
>
> On 01/26/2010 07:35 PM, Brian Stansberry wrote:
>> This tells me we have a pretty major hole in our integration testing.
>> For major functionality there should be at least some smoke tests in the
>> AS testsuite to validate that the integration works.
>>
>> https://jira.jboss.org/jira/browse/JBAS-7657
>>
>> On 01/26/2010 03: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
>>>
>>
>


-- 
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat



More information about the jboss-development mailing list