JHipster does not use lombok. Why?

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • generator-jhipster-custom-server-side-blueprint-private

    The main goal is to slight change how the code and test from Entity, Service, Mapper, DTO and Controller are generated.

  • generator-jhipster-custom-server-side-blueprint-private

  • JHipster

    JHipster, much like Spring initializr, is a generator to create a boilerplate backend application, but also with an integrated front end implementation in React, Vue or Angular. In their own words, it "Is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures."

  • I found an issue at jhipster generated project that list the the reasons to not use lombok. I will quote some of them:

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • mamazinha-baby

    The profile microservice from mamazinha app

  • source: Nap.java

  • Lombok

    Very spicy additions to the Java programming language.

  • After I run the JHipster generator for the first time I realized that the back end implemented with spring boot doesn't use Lombok. So I decided to customize the generated code to use lombok than I realized it wasn't the best way to use JHipster.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts