- remove globally installed "regular" JHipster
npm unlink -g generator-jhipster - in the "generator-jhipster" folder:
npm link(this will link this local folder to global npm node_modules) - in the "blueprint" folder:
npm link generator-jhipster(this way your locally developed blueprint will also use your locally developed JHipster) - in the "blueprint" folder:
npm link - in the "app" folder:
npm link generator-jhipster;npm link <your-blueprint> - now, when you use
jhipster --blueprints <your-blueprint>, it will use "double-linked" JHipster and your blueprint, which is important - if any of the steps is missed, you could end up using "upstream" JHipster and struggling to understand why
Simple:
jhipster entity <entity-name>
More advanced examples:
When you changed JDL for entity and want to only re-generate given entity:
jhipster jdl --json-only --skip-install --ignore-application application.jdl
and then:
jhipster entity --regenerate --skip-install <entity-name>