Bump. The situation here is that Axis2 is getting a lot of community requests for a release due to security scanners showing outdated jars - rightly or wrongly. We are getting several Jira issues related to security opened per month.
I'd be willing to become a committer to help push an Axiom release forward. Furthermore, Axis needs to file a quarterly report to the Apache board next week. Project chairs are required to subscribe to the board list, and my take is that a large portion of what the board does is roll calls on low activity projects. Moving projects to the attic happens every month. I mention that because I don't want to have to put things in the Axis board report such as "we are awaiting an Axiom release but got no response on their dev list". Regards, Robert On Fri, May 14, 2021 at 10:44 AM robertlazarski <robertlazar...@gmail.com> wrote: > Hello Web Services project, > > I am the current chair of Axis, and the Axis2 Java project is preparing > for an upcoming release of 1.8. > > Axis2 requires snapshots builds of these Web Services projects below. > Ideally, Axis2 wouldn't release with snapshots since the source of the > release would compile with changing dependencies. > > neethi: 3.1.2-SNAPSHOT > woden.version: 1.0M11-SNAPSHOT > axiom.version: 1.3.0-SNAPSHOT > > Axis2 builds ok with neethi 3.1.1 and woden.version 1.0M10; so really we > just need an Axiom release. > > BTW, I am trying to upgrade Axis2 to the current Glassfish release, 3.0.1. > Concerning Axiom, the problem is that one of our Axis2 classes extends the > Axiom DataHandlerWrapper class. > > I got stuck on the xjc tests, so I created AXIOM-506 that lists the steps > I took. > > Thanks, > Robert >