2 Replies Latest reply on Jan 27, 2010 10:17 AM by thomas.diesler

    Update to jboss-cl-2.2.x stable release

    thomas.diesler

      In order to meet the AS M2 deadline for component freeze (this week) we need to work on

       

      https://jira.jboss.org/jira/browse/JBOSGI-279

       

      Ales, can we possibly agree on a strategy today so that this issue can get resolved and AS can do the required QA cycles in time.

       

      A failure to resolve this issue in time 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. 

       

       

      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.

        • 1. Re: Update to jboss-cl-2.2.x stable release
          alesj

          Since we're talking about AS_M2, which already inculudes a bunch of MC Alphas,

          my suggestion would be to simply create a new CL 2.2.0.Alpha1 with whatever state it is in now.

          It can even include your fragments hack, since it's Alpha, and as such can (actually should) be easily changed.

           

          This simplifies things to the extent that the new CL release is first locally tested, with both

          * current AS trunk

          * current OSGi MC facade/framework

           

          If there is some issue, let me know, and we'll find a solution.

          If not, we're set to go. :-)

           

          OK?

          • 2. Re: Update to jboss-cl-2.2.x stable release
            thomas.diesler

            Yes, this is fine with me.

             

            I'll rollback the changes that I made yesterday to Branch_2_0 and you could cut the release from trunk.

            You may be pleased to hear that my "fragment hack" is also not part of trunk anymore.

             

            http://community.jboss.org/message/520294#522364