The inconistency of maven artifacts from axis2 1.1 release is
giving us a lot of troubles. What should we do at this point?
Thanks,
Raymond
I'm not sure we can do much but wait. Moving forward, though, we need
to come up with a longer term approach to this problem, i.e. the
number of dependencies introduced by extensions. To be fair, I don't
think this a problem with Axis (we run into this with other
extensions; it's our fault for relying on SNAPSHOT/too-new versions).
As these types of problems are bound to come up in the future due to
our design as an extensible infrastructure, my proposal would be to
modularize our releases further. Specifically, decouple the release
of the kernel from extensions. Our release process is mostly set up
for this today. Under this scenario, kernel could be released either
prior to or alongside extensions that are ready but would not be
bound to the availability of particular extensions.
One issue that could be raised is whether the scenario of no
extensions being ready renders a kernel release less than compelling.
My view is that a separate kernel release would be useful for a
variety of reasons, including providing a stable binary with which
people can develop extensions. In addition, applications developers
would still be able to use previous releases. Also, perhaps less
important, the kernel does provide useful function by itself,
particularly for those who want to highly customize it.
This approach would have the additional positive effect of
introducing a bit more stability for extensions developers as well as
allow particular extensions to be released quicker as they are not
coupled with others.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
