Geronimo Mail 2.1 in TomEE 10.x ?
Hi all, I was looking in more depth into the mime4j cve reported by grype for 9.1.x and 10.0.x - the spec jar contains a shade of mime4j but doesn't use anything of it. After going down the rabbit hole (just a bit) and chatting with Romain, we noticed, that mail spec 1.5 was created from a version of 1.4, which missed a few fixes (which introduced mime4j and fixed things in the mime type spec part). This is the reason for mime4j not being used in the spec since 1.5+. 1.6 was created from 1.5 and the current 2.1 from 1.6. Since TomEE switched to Eclipse specs (for most APIs), I am wondering, if we want to switch to Eclipse Mail + Impl and drop Geronimo Mail in TomEE? Alternative would be to diff Geronimo Mail 1.4 vs 1.6, see the functional difference regarding the mime type bugs fixed and port that to 2.1. Not an actual blocker but something we should consider in the long run. Thoughts? Gruß Richard
Re: AMQ6 in TomEE 10
JakartaEE 11 has 17 as a baseline for EE10 it is only 11. Ursprüngliche Nachricht Von: Alex The Rocker Datum: 31.03.24 13:22 (GMT+01:00) An: dev@tomee.apache.org Betreff: Re: AMQ6 in TomEE 10 Huge +1 for AMQ6.Requiring Java 17+ isn't a problem, since (unless I'm mistaken)Jakarta EE 10 requires Java 17.Thanks,AlexLe dim. 31 mars 2024 à 11:59, Thomas Andraschko a écrit :>> If we are allowed to set baseline to +17, im ok with it.> New user can just use 17 and existing users can easily upgrade Java when> they already migrate their whole code to Jakarta.>> Richard Zowalla schrieb am So., 31. März 2024, 11:31:>> > Hi all,> >> > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully> > Jakarta compatible (currently running a CI build on a related branch).> > However, it requires Java 17 as a baseline (meh).> >> > Since EE10 targets Java 11+ (and not 17+), the question would be, if we> > can/want to upgrade? From a spec perspective, I assume, that we cannot.> >> > Why AMQ6: It would enable us to drop some of our shaded dependencies> > (and would be a thing for EE11 anyway).> >> > I am not familiar with the TCK requirements or if it is possible to> > only support one JVM runtime for certification? At a first glance at> > [1], there are vendors (fujitsu), who only did the TCK runs on Java 17,> > but I am not familiar with the actual details of the process.> >> > Happy to get some thoughts on it.> >> > (Not planning to have such a change in the proposed milestone, just> > want to get some thoughts on it)> >> > Gruß> > Richard> >> >> > [1] https://jakarta.ee/compatibility/certification/10/> >
Re: AMQ6 in TomEE 10
JakartaEE 11 has 17 as a baseline for EE10 it is only 11. Ursprüngliche Nachricht Von: Alex The Rocker Datum: 31.03.24 13:22 (GMT+01:00) An: dev@tomee.apache.org Betreff: Re: AMQ6 in TomEE 10 Huge +1 for AMQ6.Requiring Java 17+ isn't a problem, since (unless I'm mistaken)Jakarta EE 10 requires Java 17.Thanks,AlexLe dim. 31 mars 2024 à 11:59, Thomas Andraschko a écrit :>> If we are allowed to set baseline to +17, im ok with it.> New user can just use 17 and existing users can easily upgrade Java when> they already migrate their whole code to Jakarta.>> Richard Zowalla schrieb am So., 31. März 2024, 11:31:>> > Hi all,> >> > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully> > Jakarta compatible (currently running a CI build on a related branch).> > However, it requires Java 17 as a baseline (meh).> >> > Since EE10 targets Java 11+ (and not 17+), the question would be, if we> > can/want to upgrade? From a spec perspective, I assume, that we cannot.> >> > Why AMQ6: It would enable us to drop some of our shaded dependencies> > (and would be a thing for EE11 anyway).> >> > I am not familiar with the TCK requirements or if it is possible to> > only support one JVM runtime for certification? At a first glance at> > [1], there are vendors (fujitsu), who only did the TCK runs on Java 17,> > but I am not familiar with the actual details of the process.> >> > Happy to get some thoughts on it.> >> > (Not planning to have such a change in the proposed milestone, just> > want to get some thoughts on it)> >> > Gruß> > Richard> >> >> > [1] https://jakarta.ee/compatibility/certification/10/> >
Re: AMQ6 in TomEE 10
From EE10 spec perspective, it requires 11+ , see https://jakarta.ee/specifications/platform/10/ Am 31. März 2024 13:21:56 MESZ schrieb Alex The Rocker : >Huge +1 for AMQ6. > >Requiring Java 17+ isn't a problem, since (unless I'm mistaken) >Jakarta EE 10 requires Java 17. > >Thanks, >Alex > > >Le dim. 31 mars 2024 à 11:59, Thomas Andraschko > a écrit : >> >> If we are allowed to set baseline to +17, im ok with it. >> New user can just use 17 and existing users can easily upgrade Java when >> they already migrate their whole code to Jakarta. >> >> Richard Zowalla schrieb am So., 31. März 2024, 11:31: >> >> > Hi all, >> > >> > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully >> > Jakarta compatible (currently running a CI build on a related branch). >> > However, it requires Java 17 as a baseline (meh). >> > >> > Since EE10 targets Java 11+ (and not 17+), the question would be, if we >> > can/want to upgrade? From a spec perspective, I assume, that we cannot. >> > >> > Why AMQ6: It would enable us to drop some of our shaded dependencies >> > (and would be a thing for EE11 anyway). >> > >> > I am not familiar with the TCK requirements or if it is possible to >> > only support one JVM runtime for certification? At a first glance at >> > [1], there are vendors (fujitsu), who only did the TCK runs on Java 17, >> > but I am not familiar with the actual details of the process. >> > >> > Happy to get some thoughts on it. >> > >> > (Not planning to have such a change in the proposed milestone, just >> > want to get some thoughts on it) >> > >> > Gruß >> > Richard >> > >> > >> > [1] https://jakarta.ee/compatibility/certification/10/ >> >
Re: AMQ6 in TomEE 10
Huge +1 for AMQ6. Requiring Java 17+ isn't a problem, since (unless I'm mistaken) Jakarta EE 10 requires Java 17. Thanks, Alex Le dim. 31 mars 2024 à 11:59, Thomas Andraschko a écrit : > > If we are allowed to set baseline to +17, im ok with it. > New user can just use 17 and existing users can easily upgrade Java when > they already migrate their whole code to Jakarta. > > Richard Zowalla schrieb am So., 31. März 2024, 11:31: > > > Hi all, > > > > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully > > Jakarta compatible (currently running a CI build on a related branch). > > However, it requires Java 17 as a baseline (meh). > > > > Since EE10 targets Java 11+ (and not 17+), the question would be, if we > > can/want to upgrade? From a spec perspective, I assume, that we cannot. > > > > Why AMQ6: It would enable us to drop some of our shaded dependencies > > (and would be a thing for EE11 anyway). > > > > I am not familiar with the TCK requirements or if it is possible to > > only support one JVM runtime for certification? At a first glance at > > [1], there are vendors (fujitsu), who only did the TCK runs on Java 17, > > but I am not familiar with the actual details of the process. > > > > Happy to get some thoughts on it. > > > > (Not planning to have such a change in the proposed milestone, just > > want to get some thoughts on it) > > > > Gruß > > Richard > > > > > > [1] https://jakarta.ee/compatibility/certification/10/ > >
Re: AMQ6 in TomEE 10
If we are allowed to set baseline to +17, im ok with it. New user can just use 17 and existing users can easily upgrade Java when they already migrate their whole code to Jakarta. Richard Zowalla schrieb am So., 31. März 2024, 11:31: > Hi all, > > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully > Jakarta compatible (currently running a CI build on a related branch). > However, it requires Java 17 as a baseline (meh). > > Since EE10 targets Java 11+ (and not 17+), the question would be, if we > can/want to upgrade? From a spec perspective, I assume, that we cannot. > > Why AMQ6: It would enable us to drop some of our shaded dependencies > (and would be a thing for EE11 anyway). > > I am not familiar with the TCK requirements or if it is possible to > only support one JVM runtime for certification? At a first glance at > [1], there are vendors (fujitsu), who only did the TCK runs on Java 17, > but I am not familiar with the actual details of the process. > > Happy to get some thoughts on it. > > (Not planning to have such a change in the proposed milestone, just > want to get some thoughts on it) > > Gruß > Richard > > > [1] https://jakarta.ee/compatibility/certification/10/ >
Re: [PR] Regenerated BOMs after dependency upgrades (tomee)
rzo1 merged PR #1116: URL: https://github.com/apache/tomee/pull/1116 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Regenerated BOMs after dependency upgrades (tomee)
github-actions[bot] opened a new pull request, #1116: URL: https://github.com/apache/tomee/pull/1116 Found some uncommited changes (from BOM regeneration) after running build on TomEE main -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
AMQ6 in TomEE 10
Hi all, just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully Jakarta compatible (currently running a CI build on a related branch). However, it requires Java 17 as a baseline (meh). Since EE10 targets Java 11+ (and not 17+), the question would be, if we can/want to upgrade? From a spec perspective, I assume, that we cannot. Why AMQ6: It would enable us to drop some of our shaded dependencies (and would be a thing for EE11 anyway). I am not familiar with the TCK requirements or if it is possible to only support one JVM runtime for certification? At a first glance at [1], there are vendors (fujitsu), who only did the TCK runs on Java 17, but I am not familiar with the actual details of the process. Happy to get some thoughts on it. (Not planning to have such a change in the proposed milestone, just want to get some thoughts on it) Gruß Richard [1] https://jakarta.ee/compatibility/certification/10/
