Hey folks: Can we do an official transports release to coincide with Axis2 1.5? Right now there are SNAPSHOT dependencies in there that I'd like to get rid of.
Is the codebase in OK shape to ship? What should we call it, version-wise? Anyone want to volunteer to manage the release? A suggestion - for this first release, let's start all the transports at 1.0, and then make sure that each one can be released independently. In other words, there should be nothing to prevent axis2-http-transport from being at 1.5 while axis2-jms-transport is at 3.0. If we want to release the big glommed-together transport jar with everything in it, that would also version independently, and we'd have to be very clear in the release notes which versions of which transports were contained therein. Personally, I'd be in favor of getting rid of the unified transport jar entirely, and perhaps just giving people tools to put multiple transports together in a single jar with Maven if they feel like it. Thoughts? Thanks, --Glen
