ppalaga commented on issue #293: Think about consolidating enforcing rules URL: https://github.com/apache/camel-quarkus/issues/293#issuecomment-546399814 > One of the problem I had with scripts in the past was that some scripts were applied according to the name of the artifact or based of a presence of a file and that logic is embedded into the script instead of being declarative through XML and I spent quite a few time finding out the reason of my build not doing what I was supposed. Thanks for explaining why you believe that the plugin solution is better. I think the property of being poorly written is not inherent to groovy scripts. It is rather a mistake of some particular author (maybe me). I dare to say that the same kind of mistake can happen when writing a plugin. I see that there is a clear majority for migrating the checks to plugin mojos and I am not going to force my view. Still, it would be nice to see the benefits. Yes, this is Maven and the most common way to perform tasks is to write plugins. Does that mean that we need a plugin for every single task? You seem to affirm, I do not. Having ad hoc groovy scripts is OK. They are easier to write and maintain, they are faster to run compared to a self-hosted plugin. That's it. Thanks for hearing me :-).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
