[cowls]

Hmm, I don't think not fully understanding existing tools and not wanting to read documentation is a good reason. You can easily add prompting with maven, gradle etc, test result reporting, source control integration is all built in.

The 150 flags you mention provide flexibility, you dont need to know them all to get started. With your custom build process, instead of finding a flag that does what you need, you need to implement what you need from scratch, and document it for future developers.

If you use a standard build tool its also easier to hire someone who already knows it, plus understanding them will help you fit into new teams easier.

Unless maybe this is for personal projects, in which case I think its probably less of an issue