[
https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902124#comment-17902124
]
Robert Lazarski commented on AXIS2-6051:
----------------------------------------
FYI, a release vote for Rampart 1.8.0 has been sent to the
java-dev@axis.apache.org mailing list - and for those only interested in Axis2,
getting this out will free up my time for a release of that after Axiom (needs
to happen first).
For Rampart users, the 1.8.0 release supports javax and Axis2 1.8.2 since the
community asked for that. Rampart 2.0.0 with jakarta support will follow Axis2
2.0.0.
The main content of the Rampart release email is to verify the data in these
links. For Rampart users interested in a version for Axis2 1.8.2, please review
and let me know if there are any showstoppers.
Git tag: https://github.com/apache/axis-axis2-java-rampart/releases/tag/v1.8.0
Distributions: https://dist.apache.org/repos/dist/dev/axis/axis2/java/rampart/
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheaxis2-1025
Site: https://axis.apache.org/axis2/java/rampart/core-staging/
> Axis2 Future Roadmap in keeping up with new Java Versions
> ---------------------------------------------------------
>
> Key: AXIS2-6051
> URL: https://issues.apache.org/jira/browse/AXIS2-6051
> Project: Axis2
> Issue Type: Wish
> Affects Versions: 1.8.0
> Reporter: Jeff Thomas
> Assignee: Robert Lazarski
> Priority: Major
> Fix For: 2.0.0
>
>
> Related to AXIS2-6035.
> Hi Robert/Andreas/Axis2 Support,
> just a general question about the realistic future of Axis2 (and by extension
> Axiom/Rampart) in keeping up with the quickly changing Java releases.
> We are getting a lot of push from our customers (and our own internal wish to
> use modern java features) to move to java 17+ ... we are hitting more and
> more walls with things like:
> * java modules
> * javax -> jakarta migration // this is a big one!
> ** jakarta.activation
> ** jakarta.validation
> ** jakarta.jms
> ** jakarta.mail
> ** jakarta.jws
> ** jakarta.jaxb
> ** ...
> * Tomcat 10 +
> * and related stuff like
> ** ActiveMQ Artemis (jakarta.jms)
> ** removal of SecurityManager in JDK 19+
> ** etc.
> The sort of general feeling is that unfortunately we are getting pulled
> towards a state of complete incompatibility between Axis2 and current
> supported JVMs / other Frameworks.
> Maybe you can give a bit of feedback about the roadmap for Axis2 and
> addressing the growing gap in dependencies? (and would welcome any info
> about Axiom/Rampart along the same lines). Good or bad news doesn't
> matter...would appreciate having some concrete statement to address our own
> internal planning about the way forward. :)
> Appreciate any info you can provide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
