Gradle init uses 'compile' for 'provided' maven dependencies

(Lance Java) #1

Using Gradle version 2.13

I just used gradle init to generate a gradle build from a maven build and there were a couple of issues

  1. provided dependencies were mapped to the compile configuration. Now that we have the compileOnly configuration I feel that this is a better match (note my project is a java project and not a war project)

  2. Dependencies were added using the group:'foo', name:'bar', version:'1.0' notation. I’d prefer 'foo:bar:1.0. This is more of a personal preference I guess.

(Carlo Luib-Finetti) #2

Git? Gradle init, I guess :slight_smile:

(Mark Vieira) #3

There is an open ticket for this GRADLE-3436. This is a very good candidate for a pull request :wink:

I tend to agree. I’m not sure what the rationale was here other than it being more explicit and therefore a better example for folks new to Gradle.

Build errors with Gradle init: Maven to Gradle
(Lance Java) #4

Lol… Yes… Often type git at command line instead of gradle and vice versa, there’s a wire crossed somewhere in my head. Have fixed the forum post.