2 Replies Latest reply on Apr 23, 2007 12:05 PM by Tim Fox

    JBoss common vs common core, common logging etc

    Tim Fox Master

      JBM 1.2.x depends on

      common-core
      common-logging-log4j
      common-logging-spi

      but JBAS 4.2 depends on jboss/common.

      My assumption is we depend on the core, logging etc so as not to have to drag in the entire jboss common jar.

      My question is though, how do I know what version of common-core, common-logging etc is compatible with what version of jboss common?

      We are currently using common-core 2.2. JBAS 4.2 will be using jboss common 1.2.GA. How do I know if these are compatible, so we can deploy unscoped?

        • 1. Re: JBoss common vs common core, common logging etc
          Dimitris Andreadis Master

          JBoss common 1.0.x, 1.2.x is the one that comes from the JBoss AS 4.x series. For jboss HEAD/5 it was broken into common-core, common-logging-spi, etc.

          In general they "should" be compatible, but currently it's not guaranteed.

          • 2. Re: JBoss common vs common core, common logging etc
            Tim Fox Master

            Yikes.

            So we can't guarantee that an application that uses common in JBoss AS 4.x will run in JBAS 5.0 without scoping.

            Sounds nasty.

            I should revert our dependency to be jboss commons (same as AS 4.2) so *at least* we can guarantee it will run unscoped in AS 4.2.

            But this means we will have to release a different release of JBM that is guaranteed to run in JBAS 5.0 which has dependencies aligned with AS 5.0 dependencies.

            Either that, or an explicit compatibility is defined and tested somehow between the old commons and the new common core etc.