Peter Gafert

Hmm, I can try, but it's not completely trivial. So don't get frustrated :wink: (a lot of Generics juggling :wink:) There is a public interface layer defining the API and...

Since the last update here was end of 2020, I would say yes (any objections @jwcarman? I'm just guessing by now that you probably didn't find the time :wink:)

Technically this should be doable :slightly_smiling_face: But notice that there once already was #227 which pretty much suggested the same I think? However, I didn't get around to it back...

Thanks for your hard work! I just had a quick look and added some comments for things I noticed at first sight. One important thing to keep in mind is...

| EDIT# no. 2 Added relevant test to ArchUnitTestEngineTest; also, fixed a couple of bugs If there are bugs in there it would be cool if you could create a...

What we have also done in the past is committing and pushing the violation store after each CI run. A poor man's visualization can then be achieved by a simple...

I think the reason is that ArchUnit 0.10.2 is quite "ancient" :wink: ArchUnit uses the ASM library under the hood to parse bytecode and ArchUnit 0.10.2 wasn't capable of understanding...

Is there anything more we can do for this issue? To me it feels understood now and the problem should not occur anymore with current versions, right?

I haven't really thought about it so far because it didn't seem like there are too many users of just the core layer. But principally I would be open about...

I'll see if I get around to this! I do see that the core alone does provide its own value and thus it makes sense to publish it on its...