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

Robert Lazarski commented on RAMPART-454:
-----------------------------------------

Thanks for showing an interest in Rampart and offer to help, this is important 
because we are about to release Rampart 2.0.0 however there are no active Axis2 
committers who use Rampart in their own projects. 

In fact there is even a Rampart/C version that will also have a 2.0.0 release 
soon and may happen first. This is because an Axis2/C 2.0.0 release is imminent 
and now supports JSON with Android: 

https://axis.apache.org/axis2/c/rampart/  

Anyways, I need to convert rampart to run off of the upcoming Axis2 2.0.1 
release which supports openjdk 21 and jakarta. 

Since the git repo code for Axis2 2.0.1 already has a Github job for openjdk 
25, my first thoughts are that you could confirm Axis2/Java builds ok for you 
and supports your needs. 

I haven't tested Axis2/Java with jdk 25 yet though we could make it a priority 
for the 2.0.0 release, which is about ready to happen too:

https://github.com/apache/axis-axis2-java-core/actions/runs/21752673450/job/62754403546
 

> Upgrade OpenSAML to 5.x and anything else needed for jakarta support
> --------------------------------------------------------------------
>
>                 Key: RAMPART-454
>                 URL: https://issues.apache.org/jira/browse/RAMPART-454
>             Project: Rampart
>          Issue Type: Task
>            Reporter: Robert Lazarski
>            Assignee: Robert Lazarski
>            Priority: Major
>             Fix For: 2.0.0
>
>
> This Jira is to discuss the upgrades needed for a Rampart 2.0.0 release that 
> supports jakarta and Axis 2.0.0 - and to track that progress.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to