Peter Gafert

@crizzis Thanks for the initiative :smiley: But this issue really only refers to the core API method as a first step. It does not (yet) involve any rule syntax, that...

I think this is unfortunately still missing from the fluent API, even though it would be a nice addition! For the moment you will have to resort to add this...

Oh sorry, I was playing around on the branch https://github.com/TNG/ArchUnit/pull/833 :grimacing: Once that is merged (for ArchUnit 1.0.0rc1 :wink:) the method will be `predicate.test(..)`... Anyway, glad you could solve it...

Honestly, the way ArchUnit implements composability at the moment is not via traits, but via `ArchRules`. You could pretty much achieve the same thing by ``` public class OpenClassMethodsShouldNotThrowInternalClasses {...

Hey, thanks for all the hard work, but can you please put in a detailed description of **why** (I just see *no description provided*)? My problem here is: This adds...

Maybe it would be nice to have a little SonarQube library to interface ArchUnit and SonarQube :thinking: We could also integrate #425 into it. But from my point of view...

Usually I would expect the report folders of different Gradle projects to be separate :thinking: Maybe that is why this problem hasn't popped up earlier. This might be something specific...

There is probably a related issue here: #317 But yes, at the moment it is a little bit of manual work to plug something together to only check public API...

At the moment the `ViolationStore` pretty much considers the rule text as the ID, which obviously has some shortcomings :thinking: Problem so far was that I didn't see any other...

In the end that could already be a problem at the moment :thinking: Because, right now the ID principally is the rule text. So if the same rule is evaluated...