[
https://issues.apache.org/jira/browse/DBCP-589?focusedWorklogId=834081&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-834081
]
ASF GitHub Bot logged work on DBCP-589:
---------------------------------------
Author: ASF GitHub Bot
Created on: 16/Dec/22 08:20
Start Date: 16/Dec/22 08:20
Worklog Time Spent: 10m
Work Description: rzo1 commented on PR #248:
URL: https://github.com/apache/commons-dbcp/pull/248#issuecomment-1354373025
If we change the source code (which is indeed an option), it might be
required to maintain two versions of dbcp2 as the javax namespace while be
around for a long time. In the end, it would be great to have a Jakarta-ready
version of DBCP2 available - otherwise, people are forced to do some "hacky"
things to achive that.
I cannot follow regarding "binary compatibility" - maybe you can explain
that point a bit more?
Issue Time Tracking
-------------------
Worklog Id: (was: 834081)
Time Spent: 40m (was: 0.5h)
> Provide Jakarta namespace ready artifact of DBCP2
> -------------------------------------------------
>
> Key: DBCP-589
> URL: https://issues.apache.org/jira/browse/DBCP-589
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Richard Zowalla
> Priority: Minor
> Time Spent: 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.
> For DBCP2 it would require to do some small relocations:
> {code:xml}
> <relocations>
> <relocation>
> <pattern>javax.transaction</pattern>
> <shadedPattern>jakarta.transaction</shadedPattern>
> <excludes>
> <exclude>javax.transaction.xa.**</exclude>
> </excludes>
> </relocation>
> </relocations>
> {code}
> Geronimo and other EE related projects are using the relocation / shade
> approach to provide artifacts via a "jakarta" classifier.
> I will open a related PR soon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
