Hi all,
based on the discussion [1] for DBCP, I wanted to start a discussion
whether and how the Apache Commons project might/want to support the
Jakarta namespace changes.
I know, that not all commons projects are impacted by the namespaces
change, but we should make sure, that users can use rel
Thanks for your replies.
I guess, that switching the namespace leads to binary incompatibility (If I
take the definition from [1]). I cannot drop it in a running JVM / app and
expect no issues with it as the related APIs are breaking namespace changes (at
least at runtime if they aren't presen
ically),
> sadly yes.
>
> Le ven. 16 déc. 2022 à 20:14, Richard Zowalla a
> écrit :
>
> > Thanks for your replies.
> >
> > I guess, that switching the namespace leads to binary
> > incompatibility (If
> > I take the definition from [1]). I cannot d
P 3, on Java 8 for now but
>considering Java 11 maybe. Do consider that the Commons community is small
>and I would not want to support concurrent support and releases on bothe
>DBCP 2 and 3.
>
>Gary
>
>Gary
>
>On Sat, Dec 17, 2022, 14:12 Richard Zowalla wrote:
not too far in 2023 pby.
> > >
> > > Le dim. 18 déc. 2022 à 01:44, Gary Gregory a
> > > écrit :
> > >
> > > > Hi Arun,
> > > >
> > > > There's not going to be anything to pick up for a while ;-)
> > > >
> > > >
-ee-8-high-perfor
> mance>
>
>
> Le lun. 19 déc. 2022 à 21:23, Gary Gregory a
> écrit :
>
> > I feel like we're going around in circles. Do you not agree my the
> > path I previously outlined?
> >
> > Gary
> >
> > On Mon,
There is a Jakarta artifact available for Narayana: narayana-jta-jakarta
For the SPI: jboss-transaction-spi-jakarta
(because JBoss plays the namespace game with their app server ;-) )
Geronimo most likely also provides a Jakarta version or (if it is only API) can
be replaced by the Jakarta arti
Thanks a lot, Emmanuel! 🎉🎉🎉
It looks good to me!
Gruß
Richard
Am Donnerstag, dem 29.12.2022 um 22:02 +0100 schrieb Emmanuel Bourg:
> Thank you, it works perfectly now.
>
> I've pushed the changes to:
>
> https://github.com/ebourg/commons-dbcp/tree/jakarta
>
> Comments are welcome before
I guess, that it would need some tests to show, that it is working
correctly? Otherwise it would raise similar concerns as for the PR
using Maven Shading to achieve the transition.
Gruß
Richard
P.S. Build is currently failing for that one.
Am Samstag, dem 31.12.2022 um 12:15 +0100 schrieb Emma
So what do we need to move forward with this once? :-)
Gruß
Richard
Am Sonntag, dem 01.01.2023 um 17:09 +0100 schrieb Jean-Baptiste Onofré:
> It looks good to me.
>
> Thanks,
> Regards
> JB
>
> On Sat, Dec 31, 2022 at 12:15 PM Emmanuel Bourg
> wrote:
> > I've experimented with another approach
, Jan 19, 2023, 04:42 Richard Zowalla wrote:
>
> > So what do we need to move forward with this once? :-)
> >
> > Gruß
> > Richard
> >
> > Am Sonntag, dem 01.01.2023 um 17:09 +0100 schrieb Jean-Baptiste
> > Onofré:
> > > It looks good to me.
&g
Hi,
do we have any updates?
How can I help to get a dbcp version supporting Jakarta namespace?
Emmanuel outlined a possible appraoch. How can we move forward with it?
Thanks & Gruß
Richard
On 2022/12/30 12:52:45 Richard Zowalla wrote:
> Thanks a lot, Emmanuel! 🎉🎉🎉
>
> It
s a theoretical issue.
Gruß
Richard
Am Freitag, dem 26.05.2023 um 12:08 +0200 schrieb Emmanuel Bourg:
> Le 11/05/2023 à 15:56, Richard Zowalla a écrit :
> > Hi,
> >
> > do we have any updates?
> >
> > How can I help to get a dbcp version supporting Jakarta
com/application-development/java-ee-8-high-perfor
> mance>
>
>
> Le ven. 26 mai 2023 à 12:19, Richard Zowalla a
> écrit :
>
> > The current TomEE codebase still uses classes from the "managed"
> > package of dbcp2. (Thus, we are shading it for TomEE 9
David wrote something similar on the tomee dev@ list [1].
So perhaps it would be worth to just provide a jakarta capable package?
[1] https://lists.apache.org/thread/gkmrdlwo1gpbzogqvrdyq1zqqt6pompc
Am Montag, dem 19.06.2023 um 14:09 +0200 schrieb Emmanuel Bourg:
> On 26/05/2023 12:20, Romain Man
From a spec view:
Baseline for Jakarta EE 10 would be Java 11. Jakarta EE 9 is still Java 8
(namespace Change only)
Gruß
Richard
Am 21. Juli 2023 18:10:48 MESZ schrieb Elliotte Rusty Harold
:
>Absolutely not Java 17. There are really big companies still on Java
>11, and I have no idea how ma
My 2 cents are: BeanUtils is often used in the EE ecosystem EE 9.1 targets
8/11, EE 10 targets 11/17, EE 11 targets 17 or higher.
People are still doing the EE8 to 9.1/10 move (thanks to the name change). So
perhaps 11 or 17 would be a good fit for a baseline version.
Gruß
Richard
Am 14. Sep
+1 to this argunentation. We should reduce the dependency surface as much as
possible.
Am 4. November 2024 09:27:24 MEZ schrieb Emmanuel Bourg :
>Le 02/11/2024 à 13:19, Gilles Sadowski a écrit :
>
>> My question was and still is: Can modularization help?
>
>Modularization is very much needed fo
From the sideline: I am also concerned about adding dependendcies in low level
libraries for replacing only a few lines of code.
From ASF policy perspective, the veto (-1) requires a technical explanation,
cf. https://www.apache.org/foundation/voting.html#Veto
"To prevent vetoes from being use
Maybe it's time to start a separate discussion thread about the addition of the
three libraries to compress after 1.25?
Otherwise, I fear, that we will continue to see -1 and code reverts over and
over again because there seems to be no consensus here.
So maybe let's frame it as a discussiom th
+1 to sebb.
Am 2. November 2024 10:27:39 MEZ schrieb sebb :
>On Sat, 2 Nov 2024 at 09:11, Tushar Kapila wrote:
>>
>> If you only want code that is used, you can use an obfuscator? Using
>> dependencies is the way to go, IMHO. Keep concerns tight. Change in one
>> place in case of bugs and vulner
21 matches
Mail list logo
