3 Replies Latest reply on Jan 14, 2009 10:39 AM by David Lloyd

    Remoting 3: Splitting subprojects

    David Lloyd Master

      So far I've split the project as follows:

      1) Transporters are in https://svn.jboss.org/repos/jbossremoting/remoting3-transporter/trunk. After the main GA release of Remoting, I'll release a Beta of transporters that can be used with it.
      2) As per the standard for Microcontainer integration projects, the Remoting Microcontainer project (such as it is) has been moved to https://svn.jboss.org/repos/jbossremoting/remoting-mc-int/trunk.

      I'm considering also moving the protocols each to their own projects. What do you guys think? This would probably mean that the R3 api & core would have a somewhat longer release cycle, just because new features probably won't be frequently added to the core. Instead, we'd see more frequent releases of the various supporting modules - transporters, protocols, and the supporting marshallers. This would also help prevent dead code from hanging around by hiding inside of another project - something I really hate.

      On the other hand, it means a little more release work overall, which I don't mind but others might.