I mentioned two additional ideas to deal with this problem a while ago when this issue also came up:
1) Release transports and axis2 at the same time. Have one vote for both libraries. 2) Move the base, local, tcp, and http transport modules back to Axis2 and release them with Axis2. That way the transports project would only have the 'optional' transport modules and we wouldn't have to release the transports for/with Axis2. Jarek On Mon, Mar 30, 2009 at 3:20 PM, Glen Daniels <g...@thoughtcraft.com> wrote: > Hi folks: > > So I'm trying to get the transports 1.0 releases moving along, and have run > into a bit of a snag. The transports depend on axis2-kernel SNAPSHOT, for > interfaces like MessageContext, Flow, etc. - the problem is how do we do the > release when we want to release the transports before the actual Axis2 > release? We need to resolve all the SNAPSHOT dependencies for the Maven > release plugin to be happy, and for this case, we seem to have a circular > dependency chain. :( > > A couple of options off the top of my head: > > * Release transports against Axis2 1.4.1's kernel - this may not even be > possible as there may have been incompatible changes. > > * Do a Maven-only release of Axis2-kernel 1.5 - i.e. NOT a distribution but > just a release into Maven. Then use that for the Transports 1.0 releases, > and then release the Axis2 1.5 distribution after that. > > Moving forward, anyone have thoughts on how to best deal with this? One of > these options, or something else? > > Thanks, > --Glen >
