Glen Daniels wrote:
... IMO, this would be a bad idea. The goal of the kind of modularity we have, or at least one of the goals, is to enable the components to version and release at different rates. Unless there were incompatible API changes (which certainly do happen) we should be able to release several Axis2 versions during a single Rampart release cycle, or vice versa. In reality, at least so far, we have needed to rev at least Rampart (Sandesha 1.3 works fine with Axis2 1.4 - not sure about 1.5) for compatibility.
I understand that in an ideal world we wouldn't have compatibility issues, but until we get there I don't see how we can justify having a current release of Axis2 without compatible releases of at least transports and Rampart. If we do have such a release (as now), the main page should clearly state that the "current" release only supports basic web services functionality and if users need WS-Security or alternative transports they need to either use the older release or work with nightly builds (the latter probably not an option for anyone doing commercial work). That way users would at least have the information available to guide their choice.
- Dennis
