Re: [PR] Regenerated BOMs after dependency upgrades (tomee)
rzo1 merged PR #1074: URL: https://github.com/apache/tomee/pull/1074 -- 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, #1074: URL: https://github.com/apache/tomee/pull/1074 Found some uncommited changes (from BOM regeneration) after running build on TomEE 8.x branch -- 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
Re: [PR] Close #TOMEE-4263: Update Apache Santuario to 2.3.4 from 2.3.2 (xmlsec) to mitigate CVE-2023-4448 (tomee)
exabrial merged PR #1072: URL: https://github.com/apache/tomee/pull/1072 -- 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
Re: 8.0.16 release
Yep! I just logged that one and pushed a PR. Waiting on CI On Thu, Oct 26, 2023 at 9:24 AM Jamie Johnson wrote: > > Should this be included? > > TOMEE-4263: Update Apache Santuario to 2.3.4 from 2.3.2 (xmlsec) to > mitigate CVE-2023-4448 > > Not sure how to find the others without going through commit history. > > Jamie > > On Thu, Oct 26, 2023 at 8:19 AM Jonathan S. Fisher > wrote: > > > Richard, thank you sir; I assigned that ticket to myself. If anyone > > else is aware of anything else I can upgrade before release, please > > speak up :) > > > > Also good news: for whatever reason, I'm able to build > > tomee-release-tools now. The atlassian maven repository hit me with a > > rate limit briefly but it seems to have lifted. > > > > I have three questions at this point in time: > > 1. Is there a way to scan 8.0.16-SNAPHSOT before release for CVE's? > > 2. Are there CVEs we ignore? (basically ones that are present but > > don't apply to us) > > 3. I ran a build locally and got two test failures. Looks like CI did > > too: > > https://ci-builds.apache.org/job/Tomee/job/tomee-8.x-build-full-java8/lastCompletedBuild/ > > > > It doesn't look related to the EclipseLink change unless I screwed the > > pooch on something. Are these known issues by chance? > > > > On Thu, Oct 26, 2023 at 1:03 AM Richard Zowalla > > wrote: > > > > > > Might be relevant for your release preperations: > > https://issues.apache.org/jira/browse/TOMEE-4263 > > > > > > Am 26. Oktober 2023 00:11:14 MESZ schrieb "Jonathan S. Fisher" < > > exabr...@gmail.com>: > > > >Thank you, eclipselink has been updated and boms also updated. > > > > > > > >Are the tomee release tools still needed? > > > > > > > >[ERROR] Failed to execute goal on project release-tools: Could not > > > >resolve dependencies for project > > > >org.apache.openejb.tools:release-tools:jar:1.0-SNAPSHOT: Failed to > > > >collect dependencies at org.tomitribe.jamira:jamira-core:jar:0.4 -> > > > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: Failed to read > > > >artifact descriptor for > > > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: The following > > > >artifacts could not be resolved: > > > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 (absent): Could > > > >not transfer artifact > > > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 from/to > > > >atlassian ( > > https://maven.atlassian.com/content/repositories/atlassian-public/): > > > >status code: 429, reason phrase: Too Many Requests (429) -> [Help 1] > > > > > > > >I can't seem to get the artifacts from their Maven repository due to > > > >rate limiting unfortunately. > > > > > > > > > > > >On Wed, Oct 25, 2023 at 8:50 AM Richard Zowalla > > wrote: > > > >> > > > >> Feel free to update 3rd party dependencies (make sure to create a > > Jira, > > > >> so it gets into the release notes). To update the BOMs you can either > > > >> rely on the related GitHub action (will do it automatically via a PR) > > > >> or just run a quick build. > > > >> > > > >> > > > >> Am Mittwoch, dem 25.10.2023 um 08:40 -0500 schrieb Jonathan S. Fisher: > > > >> > Richard: thank you sir, I see my key in there. > > > >> > Rod: Are the docker images part of the main build? I don't use > > Docker > > > >> > professionally, so I'm not very familiar with the whole process. > > > >> > > > > >> > I see Tomcat 9.0.82 in tomee-8.x. Yeehaw! > > > >> > > > > >> > Does anyone have an issue with me updating to eclipselink 2.7.13? > > > >> > https://github.com/eclipse-ee4j/eclipselink/releases/tag/2.7.13 > > We've > > > >> > been running TomEE 8.0.15 with 2.7.13 in production for a few weeks > > > >> > and haven't seen any issues. > > > >> > > > > >> > > > > >> > On Tue, Oct 24, 2023 at 10:18 AM Rod Jenkins > > > >> > wrote: > > > >> > > > > > >> > > Is there anyway to test the keys before we deploy? We have issues > > > >> > > in the past with new keys and verifying the packages when the > > > >> > > docker images are built. > > > >> > > > > > >> > > Thanks, > > > >> > > Rod. > > > >> > > > > > >> > > > > > > >> > > > On Oct 24, 2023, at 9:06 AM, Richard Zowalla > > > >> > > > wrote: > > > >> > > > > > > >> > > > Added to https://dist.apache.org/repos/dist/release/tomee/KEYS > > > >> > > > > > > >> > > > > Am Dienstag, dem 24.10.2023 um 08:54 -0500 schrieb Jonathan S. > > > >> > > > > Fisher: > > > >> > > > > pasted here: > > > >> > > > > > > > >> > > > > -BEGIN PGP PUBLIC KEY BLOCK- > > > >> > > > > > > > >> > > > > > > mJMEV5tUvhMFK4EEACMEIwQBDFKWRWNFys17LQRo18NBQ0cJk9HitooLx1k3dGT > > > >> > > > > A > > > >> > > > > > > G2By4TUnNYaR/ranOPJ47IRVr/1E0DBy9RKayUDNFElly6kAfhn/ALMmdv68cet > > > >> > > > > 9 > > > >> > > > > > > GWkNjV/DwEGmtdXnhuGxXioxN1XkoJJNbjDCBEzx/mDDIna7w3jE2v28bXYP9kf > > > >> > > > > v > > > >> > > > > > > aLgvUdK0J0pvbmF0aGFuIFMuIEZpc2hlciA8ZXhhYnJpYWxAZ21haWwuY29tPoj > > > >> > > > > a > > > >> > > > > > > BBMTCgA+AhsBBQsJCAcCBhUICQoLAgQWAgMBAh4BAheAFiEEhxY4ohp/LDgGZHF > > > >> >
Re: 8.0.16 release
Should this be included? TOMEE-4263: Update Apache Santuario to 2.3.4 from 2.3.2 (xmlsec) to mitigate CVE-2023-4448 Not sure how to find the others without going through commit history. Jamie On Thu, Oct 26, 2023 at 8:19 AM Jonathan S. Fisher wrote: > Richard, thank you sir; I assigned that ticket to myself. If anyone > else is aware of anything else I can upgrade before release, please > speak up :) > > Also good news: for whatever reason, I'm able to build > tomee-release-tools now. The atlassian maven repository hit me with a > rate limit briefly but it seems to have lifted. > > I have three questions at this point in time: > 1. Is there a way to scan 8.0.16-SNAPHSOT before release for CVE's? > 2. Are there CVEs we ignore? (basically ones that are present but > don't apply to us) > 3. I ran a build locally and got two test failures. Looks like CI did > too: > https://ci-builds.apache.org/job/Tomee/job/tomee-8.x-build-full-java8/lastCompletedBuild/ > > It doesn't look related to the EclipseLink change unless I screwed the > pooch on something. Are these known issues by chance? > > On Thu, Oct 26, 2023 at 1:03 AM Richard Zowalla > wrote: > > > > Might be relevant for your release preperations: > https://issues.apache.org/jira/browse/TOMEE-4263 > > > > Am 26. Oktober 2023 00:11:14 MESZ schrieb "Jonathan S. Fisher" < > exabr...@gmail.com>: > > >Thank you, eclipselink has been updated and boms also updated. > > > > > >Are the tomee release tools still needed? > > > > > >[ERROR] Failed to execute goal on project release-tools: Could not > > >resolve dependencies for project > > >org.apache.openejb.tools:release-tools:jar:1.0-SNAPSHOT: Failed to > > >collect dependencies at org.tomitribe.jamira:jamira-core:jar:0.4 -> > > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: Failed to read > > >artifact descriptor for > > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: The following > > >artifacts could not be resolved: > > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 (absent): Could > > >not transfer artifact > > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 from/to > > >atlassian ( > https://maven.atlassian.com/content/repositories/atlassian-public/): > > >status code: 429, reason phrase: Too Many Requests (429) -> [Help 1] > > > > > >I can't seem to get the artifacts from their Maven repository due to > > >rate limiting unfortunately. > > > > > > > > >On Wed, Oct 25, 2023 at 8:50 AM Richard Zowalla > wrote: > > >> > > >> Feel free to update 3rd party dependencies (make sure to create a > Jira, > > >> so it gets into the release notes). To update the BOMs you can either > > >> rely on the related GitHub action (will do it automatically via a PR) > > >> or just run a quick build. > > >> > > >> > > >> Am Mittwoch, dem 25.10.2023 um 08:40 -0500 schrieb Jonathan S. Fisher: > > >> > Richard: thank you sir, I see my key in there. > > >> > Rod: Are the docker images part of the main build? I don't use > Docker > > >> > professionally, so I'm not very familiar with the whole process. > > >> > > > >> > I see Tomcat 9.0.82 in tomee-8.x. Yeehaw! > > >> > > > >> > Does anyone have an issue with me updating to eclipselink 2.7.13? > > >> > https://github.com/eclipse-ee4j/eclipselink/releases/tag/2.7.13 > We've > > >> > been running TomEE 8.0.15 with 2.7.13 in production for a few weeks > > >> > and haven't seen any issues. > > >> > > > >> > > > >> > On Tue, Oct 24, 2023 at 10:18 AM Rod Jenkins > > >> > wrote: > > >> > > > > >> > > Is there anyway to test the keys before we deploy? We have issues > > >> > > in the past with new keys and verifying the packages when the > > >> > > docker images are built. > > >> > > > > >> > > Thanks, > > >> > > Rod. > > >> > > > > >> > > > > > >> > > > On Oct 24, 2023, at 9:06 AM, Richard Zowalla > > >> > > > wrote: > > >> > > > > > >> > > > Added to https://dist.apache.org/repos/dist/release/tomee/KEYS > > >> > > > > > >> > > > > Am Dienstag, dem 24.10.2023 um 08:54 -0500 schrieb Jonathan S. > > >> > > > > Fisher: > > >> > > > > pasted here: > > >> > > > > > > >> > > > > -BEGIN PGP PUBLIC KEY BLOCK- > > >> > > > > > > >> > > > > > mJMEV5tUvhMFK4EEACMEIwQBDFKWRWNFys17LQRo18NBQ0cJk9HitooLx1k3dGT > > >> > > > > A > > >> > > > > > G2By4TUnNYaR/ranOPJ47IRVr/1E0DBy9RKayUDNFElly6kAfhn/ALMmdv68cet > > >> > > > > 9 > > >> > > > > > GWkNjV/DwEGmtdXnhuGxXioxN1XkoJJNbjDCBEzx/mDDIna7w3jE2v28bXYP9kf > > >> > > > > v > > >> > > > > > aLgvUdK0J0pvbmF0aGFuIFMuIEZpc2hlciA8ZXhhYnJpYWxAZ21haWwuY29tPoj > > >> > > > > a > > >> > > > > > BBMTCgA+AhsBBQsJCAcCBhUICQoLAgQWAgMBAh4BAheAFiEEhxY4ohp/LDgGZHF > > >> > > > > C > > >> > > > > > AwajVDNrTw0FAloq3hgFCQWj6loACgkQAwajVDNrTw2uBwIJASDBvmAQDW59SVM > > >> > > > > f > > >> > > > > > HZ27HF6CeH1OQM6fdKxfSGZmwZXBp45MsZjzO5cXh1cuJgA1jm72Wblh7PNjAxz > > >> > > > > l > > >> > > > > > 9lD4Q2o0AgkBJYXTSjXnH395kY//RPzsuibRj4Xzdx2Riwa22h6Nl/TFf1xoFDD > > >> > > > > Z > > >> > > > > > /9CBP7sNvBpSh4ZohSwr5aYCLxObxvsF/B+I2gQ
Re: [PR] Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest (tomee)
exabrial closed pull request #1073: Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest URL: https://github.com/apache/tomee/pull/1073 -- 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
Re: [PR] Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest (tomee)
exabrial commented on PR #1073: URL: https://github.com/apache/tomee/pull/1073#issuecomment-1781224310 Got it, I'll close this, thanks! -- 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
Re: [PR] Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest (tomee)
rzo1 commented on PR #1073: URL: https://github.com/apache/tomee/pull/1073#issuecomment-1781203159 I think the difference is in purpose. It should use the older version first (as it is bundled within the webapp) and than fallback to the newer version. The test typically fails due to flakyness om CI. -- 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] Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest (tomee)
exabrial opened a new pull request, #1073: URL: https://github.com/apache/tomee/pull/1073 Fix #TOMEE-4265: EarClassLoaderTest and EarWebAppFirstClassLoaderTest test failures on 8.0.16-SNAPSHOT. joda-time dependency was upgraded from 2.5 and the corresponding tests were not upgraded to 2.10.10 -- 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] Close #TOMEE-4263: Update Apache Santuario to 2.3.4 from 2.3.2 (xmlsec) to mitigate CVE-2023-4448 (tomee)
exabrial opened a new pull request, #1072: URL: https://github.com/apache/tomee/pull/1072 Close #TOMEE-4263: Update Apache Santuario to 2.3.4 from 2.3.2 (xmlsec) to mitigate CVE-2023-4448 -- 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
Re: 8.0.16 release
Richard, thank you sir; I assigned that ticket to myself. If anyone else is aware of anything else I can upgrade before release, please speak up :) Also good news: for whatever reason, I'm able to build tomee-release-tools now. The atlassian maven repository hit me with a rate limit briefly but it seems to have lifted. I have three questions at this point in time: 1. Is there a way to scan 8.0.16-SNAPHSOT before release for CVE's? 2. Are there CVEs we ignore? (basically ones that are present but don't apply to us) 3. I ran a build locally and got two test failures. Looks like CI did too: https://ci-builds.apache.org/job/Tomee/job/tomee-8.x-build-full-java8/lastCompletedBuild/ It doesn't look related to the EclipseLink change unless I screwed the pooch on something. Are these known issues by chance? On Thu, Oct 26, 2023 at 1:03 AM Richard Zowalla wrote: > > Might be relevant for your release preperations: > https://issues.apache.org/jira/browse/TOMEE-4263 > > Am 26. Oktober 2023 00:11:14 MESZ schrieb "Jonathan S. Fisher" > : > >Thank you, eclipselink has been updated and boms also updated. > > > >Are the tomee release tools still needed? > > > >[ERROR] Failed to execute goal on project release-tools: Could not > >resolve dependencies for project > >org.apache.openejb.tools:release-tools:jar:1.0-SNAPSHOT: Failed to > >collect dependencies at org.tomitribe.jamira:jamira-core:jar:0.4 -> > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: Failed to read > >artifact descriptor for > >com.atlassian.jira:jira-rest-java-client-app:jar:5.2.2: The following > >artifacts could not be resolved: > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 (absent): Could > >not transfer artifact > >com.atlassian.jira:jira-rest-java-client-app:pom:5.2.2 from/to > >atlassian > >(https://maven.atlassian.com/content/repositories/atlassian-public/): > >status code: 429, reason phrase: Too Many Requests (429) -> [Help 1] > > > >I can't seem to get the artifacts from their Maven repository due to > >rate limiting unfortunately. > > > > > >On Wed, Oct 25, 2023 at 8:50 AM Richard Zowalla wrote: > >> > >> Feel free to update 3rd party dependencies (make sure to create a Jira, > >> so it gets into the release notes). To update the BOMs you can either > >> rely on the related GitHub action (will do it automatically via a PR) > >> or just run a quick build. > >> > >> > >> Am Mittwoch, dem 25.10.2023 um 08:40 -0500 schrieb Jonathan S. Fisher: > >> > Richard: thank you sir, I see my key in there. > >> > Rod: Are the docker images part of the main build? I don't use Docker > >> > professionally, so I'm not very familiar with the whole process. > >> > > >> > I see Tomcat 9.0.82 in tomee-8.x. Yeehaw! > >> > > >> > Does anyone have an issue with me updating to eclipselink 2.7.13? > >> > https://github.com/eclipse-ee4j/eclipselink/releases/tag/2.7.13 We've > >> > been running TomEE 8.0.15 with 2.7.13 in production for a few weeks > >> > and haven't seen any issues. > >> > > >> > > >> > On Tue, Oct 24, 2023 at 10:18 AM Rod Jenkins > >> > wrote: > >> > > > >> > > Is there anyway to test the keys before we deploy? We have issues > >> > > in the past with new keys and verifying the packages when the > >> > > docker images are built. > >> > > > >> > > Thanks, > >> > > Rod. > >> > > > >> > > > > >> > > > On Oct 24, 2023, at 9:06 AM, Richard Zowalla > >> > > > wrote: > >> > > > > >> > > > Added to https://dist.apache.org/repos/dist/release/tomee/KEYS > >> > > > > >> > > > > Am Dienstag, dem 24.10.2023 um 08:54 -0500 schrieb Jonathan S. > >> > > > > Fisher: > >> > > > > pasted here: > >> > > > > > >> > > > > -BEGIN PGP PUBLIC KEY BLOCK- > >> > > > > > >> > > > > mJMEV5tUvhMFK4EEACMEIwQBDFKWRWNFys17LQRo18NBQ0cJk9HitooLx1k3dGT > >> > > > > A > >> > > > > G2By4TUnNYaR/ranOPJ47IRVr/1E0DBy9RKayUDNFElly6kAfhn/ALMmdv68cet > >> > > > > 9 > >> > > > > GWkNjV/DwEGmtdXnhuGxXioxN1XkoJJNbjDCBEzx/mDDIna7w3jE2v28bXYP9kf > >> > > > > v > >> > > > > aLgvUdK0J0pvbmF0aGFuIFMuIEZpc2hlciA8ZXhhYnJpYWxAZ21haWwuY29tPoj > >> > > > > a > >> > > > > BBMTCgA+AhsBBQsJCAcCBhUICQoLAgQWAgMBAh4BAheAFiEEhxY4ohp/LDgGZHF > >> > > > > C > >> > > > > AwajVDNrTw0FAloq3hgFCQWj6loACgkQAwajVDNrTw2uBwIJASDBvmAQDW59SVM > >> > > > > f > >> > > > > HZ27HF6CeH1OQM6fdKxfSGZmwZXBp45MsZjzO5cXh1cuJgA1jm72Wblh7PNjAxz > >> > > > > l > >> > > > > 9lD4Q2o0AgkBJYXTSjXnH395kY//RPzsuibRj4Xzdx2Riwa22h6Nl/TFf1xoFDD > >> > > > > Z > >> > > > > /9CBP7sNvBpSh4ZohSwr5aYCLxObxvsF/B+I2gQTEwoAPgULCQgHAgYVCAkKCwI > >> > > > > E > >> > > > > FgIDAQIeAQIXgAUJDxWK5RYhBIcWOKIafyw4BmRxQgMGo1Qza08NBQJi12J8Ahs > >> > > > > D > >> > > > > AAoJEAMGo1Qza08N2hoCCQGJD79oA4k1FDY+cStkLQS8QkvTpS8xZScNRKwIW1l > >> > > > > v > >> > > > > uBKrHpfzYa7RHFh6rdbW5D+07+pNvNBg8o03+h+vr4ezqQIJAUwYTOJZlBIXeuj > >> > > > > f > >> > > > > 4LngH6C0Hc6bb0FtdMh9bHC82Iv7KSIlXcq8PZgrkWMADUu0yeJhLPXQXBzvnej > >> > > > > C > >> > > > > z6dlmR9uiNgEExMKAD4CGwEFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQSHFji > >> > > > > i > >> > >
Re: OWB4 branch - how to proceed with EE10 work?
Just a short update: I am waiting for the Johnzon vote to pass and will than integrate the PR on main, so we can start working on setting up all the TCKs and fixing what is broken and implement, what needs to be implemented. Gruß Richard Am Mittwoch, dem 18.10.2023 um 16:30 +0200 schrieb benedict: > +1 from me, I am currently porting some apps to JakartaEE. I would > be happy to test with a M1 version of tomee-10. > Ursprüngliche Nachricht Von: Richard Zowalla > Datum: 18.10.23 15:48 (GMT+01:00) An: > dev@tomee.apache.org Betreff: Re: OWB4 branch - how to proceed with > EE10 work? Hi all,we made some progress on the full build. Here it > is: [1]. The PR is here: [2]## Some notes:- @struberg fixed an issue > in OpenJPA, which was discovered during theTomEE full build.- I fixed > all JAX-WS related failures by fixing our dependency treeregarding > JAXB usage. So this is working now now (but not backed by TCKresults > yet as CXF4 isn't EE10 ready atm)- The only open and failing test for > the full > build:org.superbiz.moviefun.MoviesHtmlUnitTest.testShouldMakeSureWeba > ppIsWorkinin the arquillian adaptors example. @struberg thinks, that > it might berelated to a change in OWB [3]. As suggested, I added a > profile for theCDI-TCK, so we can fix that separatly.- If you look > into [1], you see some flaky tests in the MP metricssection. These > tests are passing locally.## Question / Action items:I tend to add an > exclude for the example, which is failing due to theOWB change until > there is an OWB fix (or property?) available.What do you folks think? > Any objections in merging it and start workingon the TCK(s) based on > a (than) green full build using EE10 APIs /impls? We might be also > able to run against the EE9.1 TCK from main...After our dependencies > aren't SNAPSHOT anymore, we might want to cut aM1 even though it > doesn't pass the TCK yet?GrußRichard[1] > https://github.com/apache/tomee/pull/1066[2] > https://ci-builds.apache.org/job/Tomee/job/pull-request-manual/54/[3]https://github.com/apache/openwebbeans/commit/4e4962a69064585d146c71bb387a8395455e88b5Am > Mittwoch, dem 11.10.2023 um 22:23 +0200 schrieb > BenedictEisenkrämer:> > > > +1 for merging the PR, as to not loose > sight of what is working> > > > and> > > > what is not.> > > > I > think it is a good idea to add the profile for it and fix the> > > > > > > tests > on > > > > main.> > > > > > > > On 09.10.23 13:40, > Richard Zowalla wrote:> > > > > > > > I agree with you, Thomas ;-)> > > > > > > > > > > > > > > > > The initial problem is/was, that > upgrading to EE-10> > > > > > > > APIs has a > > > > lot > > of> > > > > > > > > cross dependencies. At least the full build is green,> > > > > > > > > so it is > > > > only > > the> > > > > > > > CDI TCK, which > is currently failing.> > > > > > > > > > > > > > > > If we add a > profile for it (similar to johnzon), we can> > > > > > > > just > > > > > > > continue> > > > > > > > to work with smaller units.> > > > > > > > > > > > > > > > > Gruß> > > > > > > > Richard> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Am Montag, dem 09.10.2023 > um 13:29 +0200 schrieb Thomas> > > > > > > > > > > > Andraschko:> > > > > > > > > > > > > IMO we should really just merge the PR soon.> > > > > > > > > > > > > Its t big > > > > > > to > > > work on> > > > > > > > > > > > > something.> > > > > > > > > > > > Then create some JIRA > tasks for everything> > > > > > > > > > > > still open and > > > > > > > close > > > some> > > > > > > > > > > > current resolved ones.> > > > > > > > > > > > > > > > > > > > > > > > > I can have a look at the > failing CDI tests> > > > > > > > > > > > then, but maybe > > > > > > > mark > > > or> > > > > > > > > > > > romain> > > > > > > > > > > > > has time. They have more knowledge :D> > > > > > > > > > > > > > > > > > > > > > > > > Am Fr., 6. Okt. 2023 um 10:19 Uhr schrieb> > > > > > > > > > > > > Richard Zowalla> > > > > > > > > > > > > :> > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for your fast repsonse, Thomas!> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It compiled because I cherry > picked> > > > > > > > > > > > > > > > some changes from > > > > > > > > > the >> > > > > > > > > > > > > > > > > > > previous> > > > > > > > > > > > > > > > > EE-> > > > > > > > > > > > > > > > 10 branch in which > the annoations were> > > > > > > > > > > > > > > > changed.> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I just removed > those tests.> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Gruß> > > > > > > > > > > > > > > > Richard> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Am Freitag, dem > 06.10.2023 um 10:04> > > > > > > > > > > > > > > > +0200 schrieb > > > > > > > > > Thomas> > > > > > > > > > > > > > > > Andraschko:> > > > > > > > > > > > > > > > > > > > > Hi Richard,> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
