[
https://issues.apache.org/jira/browse/DBCP-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104759#comment-18104759
]
Gary D. Gregory commented on DBCP-589:
--------------------------------------
Whichever approach we take to provide Jakarta support, it will not break binary
compatibility within a major release line, in this case, 2.x.
Since the changes appear to be focused solely on the `managed` package, it is
likely that we can convert the project to a Maven multi-module project and add
a `managed.jakarta` package.
Alternatively, a more disruptive 3.0 release could switch from `javax` to
`jakarta`, along with changing the package name from dbcp2 to dbcp3 and
updating the Maven coordinates.
> Provide Jakarta namespace ready artifact of DBCP2
> -------------------------------------------------
>
> Key: DBCP-589
> URL: https://issues.apache.org/jira/browse/DBCP-589
> Project: Commons DBCP
> Issue Type: Wish
> Affects Versions: 2.9.0
> Reporter: Richard Zowalla
> Priority: Minor
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently, we are using a shaded and relocated version of DBCP2 in TomEE to
> have a Jakarta namespace variant of DBCP2.
> Would be nice to have a Jakarta ready artifact.
> See https://lists.apache.org/thread/kzoox2hkb484gyj1z13rn42xko2bp29w
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
