Peter Gafert

Yeah, that was my plan :slightly_smiling_face: I would just introduce `archunit-core` and let the artifact `archunit` depend on it. That way no dependencies out there would need to be adjusted...

But I would probably only extract `core` for now until there is a further request :slightly_smiling_face: Keep it simple :man_shrugging:

Quick update, I tried this time-boxed but unfortunately ran into some problems :disappointed: The code can be split quite easily, but the repackaging of the libraries causes some headache. Unfortunately,...

Honestly, I've never considered using `archunit_ignore_patterns.txt` and `FreezingArchRule` together :thinking: Because `FreezingArchRule` in the end is a more sophisticated version of the former, since `FreezingArchRule` automatically removes the ignores once...

Ah, I see, thanks a lot for sharing :smiley: I think that this simply is a use case I never came by, to distribute `FreezingArchRules` at that scale as a...

I think I'll have some time to look into this this weekend. So ping me if you've already started working on it, otherwise I would try to tackle it :slightly_smiling_face:

Thanks for raising the issue! You're right, at the moment "pre-filtering" for more than just the location is not really possible. I also played around a little with excluding synthetic...

Ah, okay. But this is a little different, because it will filter the set of classes completely after the import. Which means that dependencies to the filtered classes will e.g....

Unfortunately I think at the moment the cycle algorithm of ArchUnit is not public API for use cases outside of the slices API :thinking: So if you only want to...

I think there is great value for libraries to have some sort of guard for public API types. In fact ArchUnit itself has its own convention: `@PublicAPI(usage = ACCESS/INHERITANCE)` which...