Mustapha Zorgati
Mustapha Zorgati
> Nevermind, of course wrong Java version man_facepalming I thought it was set to 11, but it was actually set to 17. Still, would have been nice to get some...
I've just updated the branch and did some testing. Now the behavior is a little different. Unfortunately the tests still fail when the store files are generated through different ways...
Hi @codecholeric, sorry for the late response. The last two weeks have been rather busy. > When I use 1.0.0-rc1 and delete the existing ViolationStore, then when I create a...
Hey @codecholeric, > My problem is that I can't reproduce it anymore thinking I pulled your latest changes, then recompiled everything, ran the test from IntelliJ, the store was created,...
> Thanks a lot for the extensive info heart_eyes That helps a lot! You're welcome! > On the first sight it looks like each environment detects another cycle within pro.taskana.common.internal.configuration.TaskanaConfigurationInitializer...
>Okay, this was quite the rabbit hole joy The first thing I noticed was that while some cycles between these classes were missing, this would not happen anymore if I...
I am very sorry, but I have to reopen this issue. My previous testing method is flawed and did not target the "enemy": AspectJ. What I've tested is that maven...
I can totally understand your reasoning. Thanks for the explanation. :)
Just paste t twice. `2p` or `2"p"`
You're welcome my friend :smile: