wangmiaomiao 21d6b4f9b4 解决springmvc因版本造成的路径通配问题 | 8 月之前 | |
---|---|---|
bin | 11 月之前 | |
developData | 11 月之前 | |
gradle | 11 月之前 | |
logs | 8 月之前 | |
src | 8 月之前 | |
.gitignore | 8 月之前 | |
README.md | 11 月之前 | |
api.http | 11 月之前 | |
build.gradle | 8 月之前 | |
checkstyle.xml | 11 月之前 | |
gradle.properties | 8 月之前 | |
gradlew | 11 月之前 | |
gradlew.bat | 11 月之前 | |
package-lock.json | 11 月之前 | |
package.json | 11 月之前 | |
pageExtraInfo.txt | 11 月之前 | |
settings.gradle | 11 月之前 | |
sonar-project.properties | 11 月之前 |
This application was generated using JHipster 7.4.0, you can find documentation and help at https://www.jhipster.tech/documentation-archive/v7.4.0.
To start your application in the dev profile, run:
./gradlew
For further instructions on how to develop with JHipster, have a look at Using JHipster in development.
JHipster Control Center can help you manage and control your application(s). You can start a local control center server (accessible on http://localhost:7419) with:
docker-compose -f src/main/docker/jhipster-control-center.yml up
To build the final jar and optimize the carbonlibra application for production, run:
// for normal 160-test
./gradlew -Pprod clean bootJar
// for online-prod
./gradlew -Pprod -Pthin clean thinJar
To ensure everything worked, run:
java -jar build/libs/*.jar
Refer to Using JHipster in production for more details.
To package your application as a war in order to deploy it to an application server, run:
./gradlew -Pprod -Pwar clean bootWar
cd ../data/projects/cnsp
kill -15 $(cat pid.file)
// for the 160-test
nohup ./jdk-11.0.11+9-jre/bin/java -jar cnsp-java.jar >/dev/null 2>&1 & echo $! > ./pid.file &
// for the online-prod
nohup java -jar cnsp-java.jar >/dev/null 2>&1 & echo $! > ./pid.file &
To launch your application's tests, run:
./gradlew test integrationTest jacocoTestReport
Performance tests are run by Gatling and written in Scala. They're located in src/test/gatling.
To use those tests, you must install Gatling from https://gatling.io/.
For more information, refer to the Running tests page.
Sonar is used to analyse code quality. You can start a local Sonar server (accessible on http://localhost:9001) with:
docker-compose -f src/main/docker/sonar.yml up -d
Note: we have turned off authentication in src/main/docker/sonar.yml for out of the box experience while trying out SonarQube, for real use cases turn it back on.
You can run a Sonar analysis with using the sonar-scanner or by using the gradle plugin.
Then, run a Sonar analysis:
./gradlew -Pprod clean check jacocoTestReport sonarqube
For more information, refer to the Code quality page.
You can use Docker to improve your JHipster development experience. A number of docker-compose configuration are available in the src/main/docker folder to launch required third party services.
For example, to start a mysql database in a docker container, run:
docker-compose -f src/main/docker/mysql.yml up -d
To stop it and remove the container, run:
docker-compose -f src/main/docker/mysql.yml down
You can also fully dockerize your application and all the services that it depends on. To achieve this, first build a docker image of your app by running:
./gradlew bootJar -Pprod jibDockerBuild
Then run:
docker-compose -f src/main/docker/app.yml up -d
For more information refer to Using Docker and Docker-Compose, this page also contains information on the docker-compose sub-generator (jhipster docker-compose
), which is able to generate docker configurations for one or several JHipster applications.
To configure CI for your project, run the ci-cd sub-generator (jhipster ci-cd
), this will let you generate configuration files for a number of Continuous Integration systems. Consult the Setting up Continuous Integration page for more information.