In late 2017, JHipster was nominated for / won several awards in the tech innovation space. It is easy to see why. This tool automatically generates not only boiler plate code for full stack applications based on spring boot + front end (either react or angular at the time of this writing), but it also generates boiler plate for connecting to a number of databases, tools for front end authentication, and even user management. Each of these things is a somewhat time consuming task, and having a tool that connects all of these dots out the gate can be extremely useful. While I suspect many enterprises will struggle to use all of the abilities of a tool like this due to legacy systems, small projects, startups, and people looking to learn about how some of these technologies could definitely benefit from JHipster. I will hopefully see about tackling a project using JHipster soon.
When generating a data model from JHipster JDL, we will often declare entities with Boolean fields. I have so far abandoned H2 as a database because of liquibase issues, and both my dev and production databases will be MySQL. This is relevant to the Boolean field desire there is a long history in software development of how to store Boolean data types in a SQL database whose standards classically do not support Boolean. In the current JHipster/Liquibase incarnation, tables in MySQL are generated for us, which is really nice. The Boolean data types are stored as BIT (1). This is not a problem so far -- most developers seem to agree now that as a best practice, we should store values in databases as false = 0 and true = 1, and a BIT(1) is a great, simple way to do that. An issue arises when we try to use liquibase to set/update our database to the desired starting state. For my project, I've chosen gradle instead of maven as a build tool, and gradle has a plugin for liquiba