> Well, it's not quite that easy. The problem is that we want to release Axis2 > (the distribution assemblies) /with/ at least the HTTP and local transports > included. This puts us in a situation where we can't release either unless > the other has been released first... but only if we tightly couple the Maven > releases of the Axis2 jars to the release of the Axis2 distribution files. > > I'd like to understand the confusion that releasing Maven artifacts first > (before the distribution packages) would cause, because as I think about it > more, I think it might be a pretty reasonable solution. Release the Axis2 > 1.5 jars to the Maven repositories (those jars depend upon the transports > 1.0-SNAPSHOT version, but only for tests), then release the transport 1.0 > jars bound to those, then build and release the Axis2 1.5 distribution > assemblies (containing the 1.0 transports).
I'm sorry, I may be misunderstanding what you mean by "Maven-only" release. When you say "distribution assemblies", what are you referring to? The big omnibus distribution package that people download from the front page when they don't want to know the details? That should be considered a completely separate artifact from the components that go into it - i.e. there should *never* be a case where *anything* depends on the final distributable. It's just an assembly of other artifacts, and those artifacts should be available independent of the larger distribution. > I do not, clearly, agree with the point of view that the transports should > become truly decoupled from Axis2. I'm not sure what that would even mean, > when you think about what the transports actually do - which is take > wire-level stuff and turn it into MessageContexts to push into AxisEngine, > and vice versa. I didn't mean to imply that there should be a complete decoupling. I just think its important that any cyclical dependencies are removed, rather than papered over. Thanks, Jason > > Thanks, > --Glen > >> - Jason >> >> >> >>> 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 >>
