Build errors with Gradle init: Maven to Gradle


(Carlo Luib-Finetti) #1

Gradle Version: 3.1
Operating System and JVM version: Windows 10, Java 8

Someone gave me an example project with Java sources and some jars residing in “src/main/webapp/WEBINF/lib” and a “pom.xml” for the project. To use it as an Eclipse project I tried to convert it to a Gradle project using “gradle init” and then call task eclipse.

Two problems are manifest in the generated “build.gradle”:

  • Gradle converted the Maven scope provided into a providedCompile, which is only know when the plugin war is applied.
  • Gradle converted the Maven scope system into a system configuration which is unknown. As I noticed, with this Maven scope, there a two jars referenced which reside in directory “src/main/webapp/WEB-INF/lib”.

(Carlo Luib-Finetti) #2

Maven scope system should be converted to providedCompile, no?

Then, in a former post (Gradle init uses 'compile' for 'provided' maven dependencies) I asked to replaced the noisy (Maven-like) dependency notations to the short Gradle style. Someone of the Gradle team acknowledged this should indeed be done.