Re: [PR] Bump jakarta.validation:jakarta.validation-api from 3.0.2 to 3.1.0 [openwebbeans]

dependabot[bot] commented on PR #103: URL: https://github.com/apache/openwebbeans/pull/103#issuecomment-2418598813 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version,

Re: [PR] Bump jakarta.validation:jakarta.validation-api from 3.0.2 to 3.1.0 [openwebbeans]

struberg closed pull request #103: Bump jakarta.validation:jakarta.validation-api from 3.0.2 to 3.1.0 URL: https://github.com/apache/openwebbeans/pull/103 -- 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 g

Re: [PR] fix flaky test testObserverMethodsInParentOfAlternativeAndSpecialized [openwebbeans]

struberg commented on PR #100: URL: https://github.com/apache/openwebbeans/pull/100#issuecomment-2418550899 > Hi, Thank you for the response. The test failure occurs when running with different seed values using Nondex, not when running a single Nondex run multiple times. Hi!

Build failed in Jenkins: OpenWebBeans » OpenWebBeans-trunk #83

See Changes: [Richard Zowalla] OWB-1441 - Add reproducer test case [Mark Struberg] OWB-1441 fix exception if custom interceptor has no default ct [Mark Struberg] OWB-1446 move guess sample t

Re: [PR] fix flaky test testObserverMethodsInParentOfAlternativeAndSpecialized [openwebbeans]

ljmcr commented on PR #100: URL: https://github.com/apache/openwebbeans/pull/100#issuecomment-2417931331 > This code part is not intended to be used in parallel. When running the Tests in parallel, they should boot up different BeanManagers. That can be done with running those in own isolat

Re: [DISCUSS] get rid of our master branch on gitbox?

+1 On Wed, Oct 16, 2024, 11:48 Richard Zowalla wrote: > +1 > > > Am 16.10.2024 um 16:43 schrieb Thomas Andraschko < > andraschko.tho...@gmail.com>: > > > > +1 > > > > Am Mi., 16. Okt. 2024 um 16:21 Uhr schrieb Romain Manni-Bucau < > > rmannibu...@gmail.com>: > > > >> +1 > >> > >> Le mer. 16 oct.

Re: [DISCUSS] get rid of our master branch on gitbox?

+1 > Am 16.10.2024 um 16:43 schrieb Thomas Andraschko > : > > +1 > > Am Mi., 16. Okt. 2024 um 16:21 Uhr schrieb Romain Manni-Bucau < > rmannibu...@gmail.com>: > >> +1 >> >> Le mer. 16 oct. 2024 à 16:15, Mark Struberg a >> écrit : >> >>> We did switch our mainline branch in git to main some

Re: [DISCUSS] get rid of our master branch on gitbox?

+1 Am Mi., 16. Okt. 2024 um 16:21 Uhr schrieb Romain Manni-Bucau < rmannibu...@gmail.com>: > +1 > > Le mer. 16 oct. 2024 à 16:15, Mark Struberg a > écrit : > > > We did switch our mainline branch in git to main some while ago. > > Should we get rid of the old master branch on gitbox and also blo

Re: [DISCUSS] get rid of our master branch on gitbox?

+1 Le mer. 16 oct. 2024 à 16:15, Mark Struberg a écrit : > We did switch our mainline branch in git to main some while ago. > Should we get rid of the old master branch on gitbox and also blow it away > on github? > > Today I accidentally committed to the master branch, and I'd like to avoid > c

[DISCUSS] get rid of our master branch on gitbox?

We did switch our mainline branch in git to main some while ago. Should we get rid of the old master branch on gitbox and also blow it away on github? Today I accidentally committed to the master branch, and I'd like to avoid confusion. txs and LieGrue, strub