Peter Gafert

Sorry for answering so late. I have to admit that so far I have not had the chance to really try out ArchUnit in a big Scala project. But in...

Thanks for the example! But for such idiomatic cases I think it would be necessary to create something like `ArchUnit-Scala` with some specific handling :thinking: It might be possible to...

Thanks for raising the issue! First, about the lambda parameter, can you please try version `1.0.0-rc1`? Because these dependencies should be correctly dereferenced then and methods like `lambda$xxx$123` should vanish......

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 other...

Yes, checking out the difference if you use `1.0.0-rc1` would definitely be helpful :slightly_smiling_face:

I finally found some time to look into it, this is how it looked to me: 1) When I use `1.0.0-rc1` and delete the existing `ViolationStore`, then when I create...

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, ran it from...

Thanks a lot for the extensive info :heart_eyes: That helps a lot! On the first sight it looks like each environment detects another cycle within `pro.taskana.common.internal.configuration.TaskanaConfigurationInitializer` and inner classes :exploding_head:...

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...

The problem is, I think asking that it behaves the same with and without AspectJ is impossible. Because AspectJ just fundamentally changes the bytecode. And the bytecode is the source...