question" or "help wanted":war file not generated after running gradlew war

[nkc3]

Hi team,

Please suggest how to proceed further.
D:\qrapid\qrapids-dashboard>gradlew war
Downloading https://services.gradle.org/distributions/gradle-4.9-bin.zip
........................................................................

Welcome to Gradle 4.9!

Here are the highlights of this release:

• Experimental APIs for creating and configuring tasks lazily
• Pass arguments to JavaExec via CLI
• Auxiliary publication dependency support for multi-project builds
• Improved dependency insight report

For more details see https://docs.gradle.org/4.9/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)
Download https://plugins.gradle.org/m2/org/sonarqube/org.sonarqube.gradle.plugin/2.7/org.sonarqube.gradle.plugin-2.7.po
Download https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-gradle-plugin/2.1.6.RELEASE/spring-boot-gradle-plugin-2.1.6.RELEASE.pom
.....
....
Download https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-data-jpa/2.1.6.RELEASE/spring-boot-starter-data-jpa-2.1.6.RELEASE.jar

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.9/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 4m 5s
2 actionable tasks: 2 executed
D:\qrapid\qrapids-dashboard>

[alejandravv]

Hi,

It's seems that the problem is with the command you use, try to use gradlew bootWar. We always use this one and it works well for us.

Hope it will help you and we look forward to your answer.