CODEWITHSUNDEEP
gradle
ElderMael
ElderMael

Reputation: 7111

providedCompile without war plugin

I want to reuse certain filter for many projects so I want to extract it and use a single jar to just add it to any Web App.

For building I am using Gradle 1.3 and the following build.gradle file:

apply plugin: 'java'

dependencies {

    compile group:'org.slf4j', name:'slf4j-api', version:'1.7.+'

    testCompile group:'junit', name:'junit', version:'4.+'

    compile group:'org.springframework', name:'spring-web', version:'3.+'   

    compile group:'org.slf4j', name:'slf4j-log4j12', version:'1.6.+'
    compile group:'log4j', name:'log4j', version:'1.2.+'

    providedCompile group: 'javax.servlet', name: 'javax.servlet-api', version:'3.+'        

}

repositories {

    mavenCentral()

}

As you can see, I need the servlet api to compile this filter succesfully so I want to add it like a maven provided dependency.

Anyways, after running gradle build I get the following error:

Could not find method providedCompile() for arguments [{group=javax.servlet, name=javax.servlet-api, version=3.+}] on root project 'hibernate-conversation-context'.

Now, I know that I cannot use providedCompile without the WAR plugin but I need the project to be a simple JAR. Is there another way to do this?

Upvotes: 40

Views: 35538

Answers (7)

Doron Gold
Doron Gold

Reputation: 3789

As of Gradle 2.12 the issue of defining compile only dependencies is finally solved in a simple and natural manner by the new "copmpileOnly" configuration:

dependencies {
    compileOnly 'javax.servlet:servlet-api:2.5'
}

Upvotes: 13

Gerhard Schlager
Gerhard Schlager

Reputation: 3155

Take a look at the Gradle plugin propdeps from SpringSource. From the project description:

Provides additional optional and provided dependency configurations for Gradle along with Maven POM generation support.

Upvotes: 14

ginzsa
ginzsa

Reputation: 61

When you find yourself using Gradle 2.12, change 'providedCompile' to 'compileOnly'.

Upvotes: 6

Peter Borbas
Peter Borbas

Reputation: 178

To make the javadoc work I had to add this:

javadoc.classpath=sourceSets.main.compileClasspath

Upvotes: 4

Dima Gutzeit
Dima Gutzeit

Reputation: 221

There is an easier way:

configurations {    
    provided
    provided.extendsFrom(compile)
}

and then you can:

dependencies {  
    provided group: 'javax.servlet', name: 'javax.servlet-api', version:'3.+' 
}

You will also want to have the provided libraries in the generated project files of Eclipse or Idea:

idea.module.scopes.PROVIDED.plus += configurations.provided
eclipse.classpath.plusConfigurations += configurations.provided

Upvotes: 5

dty
dty

Reputation: 18998

I wrote a blog post recently which covers exactly this scenario. It also shows you how to get integration with Eclipse set up properly too.

http://blog.codeaholics.org/2012/emulating-mavens-provided-scope-in-gradle/

Upvotes: 6

Hiery Nomus
Hiery Nomus

Reputation: 17779

There is no such configuration out of the box for the java plugin. However you can build it yourself as follows:

configurations { providedCompile }

dependencies {
    providedCompile "javax.servlet:javax.servlet-api:3.+"
}

sourceSets.main.compileClasspath += configurations.providedCompile
sourceSets.test.compileClasspath += configurations.providedCompile
sourceSets.test.runtimeClasspath += configurations.providedCompile

This adds the configuration, and puts all the dependencies in there on the compile classpaths of both your main classes and test classes. You also need to add it to the runtimeClasspath, as that doesn't include the compile classpath according to the gradle DSL documentation.

Upvotes: 54

Related Questions