Unify treatment of predefined and configurable rules about arch-unit-maven-plugin HOT 4 OPEN

Great, all in one ! I can't wait to see these changes 🙂

from arch-unit-maven-plugin.

thanks for the suggestion, I think I see where you're going, and yes, it makes sense.

But one thing though, because I have a doubt on one use case : with your approach, all predefined rules have to be in PreconfiguredRules in the "official" plugin distribution, right ? so people can't add their own private preconfigured rules in a jar and reference them in the config, right ?

from arch-unit-maven-plugin.

Yes, people would not be able to reference their custom rule as a preconfigured rule, but would have to use a configurable rule 😉.
For me this seems like a natural behavior though, preconfigured rules are delivered with the plugin, if I want to plug in a custom rule, I use the configurable rule API.
I mean, you could add a rule location to preconfigured rules as well, which defaults to PreconfiguredRules, but then you kind of have configurable rule 😉

from arch-unit-maven-plugin.

yes, you're right, nobody would be totally blocked as such.

alright, let's see how this would go then ! We are very happy to get the inputs from various people, even if it means introducting a breaking change in the config. The project is still quite young, so hopefully not too many people are impacted ;-)

And if they are, maybe they can use CI-droid to replicate the changes in their many repositories !

from arch-unit-maven-plugin.