[ 
https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903697#comment-17903697
 ] 

Robert Lazarski commented on AXIS2-6051:
----------------------------------------

Update: Axis2 urgently needs a committer and there is no hyperbole in that 
statement. 

Problem: The Apache Foundation has very strict rules about having a minimum 3 
people being active and we have that - the issue is that 3 people are not 
voting consistently. 

Being a committer is merely just an ask to vote (in Axis2 you get that right 
automatically) - and from the foundations point of view, able to apply a 
security patch if no one else is available. Coding is a nice bonus but not 
mandatory as its a volunteer position. 

What needs to be solved: we need this vote to pass to release Rampart. 

https://lists.apache.org/list.html?java-dev@axis.apache.org

What I can do: If someone sends me an email to robertlazarski @ gmail 
volunteering to be a committer, I can ensure Axis2 2.0.0 gets released before 
xmas. 

> 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

Reply via email to