By default, JHipster will use the dev profile

If you run the application without Maven/Gradle, launch the “Application” class (you can probably run it directly from your IDE by right-clicking on it).

If you run the application with Maven, run ./mvnw to use our Maven Wrapper, or mvn to use your own Maven installation.

If you run the application with Gradle, run ./gradlew to use our Gradle Wrapper, or gradle to use your own Gradle installation.

When using Angular 2+ and Maven if you need to do a clean run with webpack compilation enabled for dev profile you can pass the webpack param as below

./mvnw -Pdev,webpack

Note Gradle automatically runs webpack compilation in dev profile if front end has changed (only at start up, for live reload use npm start or yarn start).

In production, JHipster has to run with the prod profile

You can run JHipster in production directly using Maven or Gradle:

With Maven, run ./mvnw -Pprod (or mvn -Pprod)

With Gradle, run ./gradlew -Pprod (or gradle -Pprod)

If you want to package your application as an executable WAR file, you should provide Maven or Gradle with a profile. E.g.,:

With Maven, run ./mvnw -Pprod package (or mvn -Pprod package)

With Gradle, run ./gradlew -Pprod bootJar (or gradle -Pprod bootJar)

When you run your production application from a WAR file, the default is to use the same profile(s) as used during packaging. If you want to override this, you can explicitly provide an alternative in VM argument:

These can be used along with both the dev and prod profiles. Please note that by default, the swagger profile is not enabled in prod and enabled in dev by setting the spring.profiles.include property in application.yml.

swagger, no-liquibase, tls are only used at runtime:

In your IDE, run your main application class with spring.profiles.active=dev,no-liquibase (please note you need to include the dev or prod profile explicitly)