[
https://issues.apache.org/jira/browse/CONFIGURATION-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827501#comment-17827501
]
Gary D. Gregory commented on CONFIGURATION-836:
-----------------------------------------------
Hello [~michieldx]
# Please read
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
# Don't break binary compatibility (BC)
If switching from javax to jakarta breaks BC, then it's a no-go for the 2.x
major release line but can be done in a future for 3.x.
If switching from javax to jakarta does not breaks BC, but breaks existing
applications, then we're in the same boat as above.
> Make configuration use jakarta instead of javax
> -----------------------------------------------
>
> Key: CONFIGURATION-836
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-836
> Project: Commons Configuration
> Issue Type: Improvement
> Reporter: Michiel
> Priority: Major
>
> I'm currently upgrading my Spring Boot application from 2 to 3 and therefor
> also switching from javax to jakarta. Unfortunately I'm using Hystrix, which
> relies on Commons Configuration, which does not support jakarta yet.
> This seems like an easy fix and makes me not have to migrate away from
> Hystrix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
