Exclude resource file from jar file

[mrodent (Mike Rodent)]

I’ve seen these and read through them…

How to exclude a file from src/main/resources from the WAR file?

Well the file path I want to exclude from WEB-INF/classes is: src/main/resources/dev.properties It’s not really that a particular expression is working unexpectedly – I’ve tried a few things that don’t seem to work, but in most I cases I think I understand why. So now I just can’t find one that does what I want and trial and error is getting tiresome. Here are some examples of what I’ve tried: //try 1 (doesn't work) exclude('../resources/dev.properties') //try 2 (doesn't affect resources co…

How can i exclude jars/dependencies from test [solved]

thx raffael for your answer. unfortunately it doesn’t work that way either. ‘testRuntime’ uses the libs/classpaths from runtime, which i want to prevent. i’ve checked it with: test { configurations.testCompile.each { println "testCompile:" + it } } i’ve solved it with a little workaround using the war plugin and a new configuration: configurations { addWarArchive } war { // additional libraries only for the war-archive. classpath configurations.addWarArchive } dependencies {…

… they don’t seem to answer my question.

I have a “production” logback configuration file logback.xml under src/main/resources… but that directory also contains the “testing” logback configuration file logback-test.xml (which logback looks for first).

When creating an executable jar I want to delete the “testing” xml file.

I tried this

jar {
	manifest {
        // PS this is the correct line for Shadow Plugin...
		attributes 'Class-Path': '/libs/a.jar'
		attributes 'Main-Class': 'core.MyMainClass'
	}
	exclude("**/resources/*test*")
}

and I tried this

jar {
	manifest {
		attributes 'Class-Path': '/libs/a.jar'
		attributes 'Main-Class': 'core.MyMainClass'
	}
	doLast {
		exclude("**/resources/*test*")
	}
}

… what am I doing wrong?

I find [here][1] that I was probably making life difficult for myself in putting these xmls under /src/main/resources … so I created a new directory under src, /logback, and put the files in there instead. I added this to the classpath (as logback says that’s where it looks for these files) by doing this:

test {
	classpath += files( 'src/logback' )
}

Interestingly, as well as meaning that logging during testing happens OK, this is enough to get the resulting executable jar to use logback OK when run.

Unfortunately, configuring the “shadowJar” task like this

shadowJar {
	 baseName = 'DocumentIndexer'
	 classifier = null
	 version = project.version
     exclude("logback/*test*")
}

or configuring “jar” task like this:

jar {
	manifest {
		attributes 'Class-Path': '/libs/a.jar'
		attributes 'Main-Class': 'core.ConsoleIOHandler'
	}
	exclude("logback/*test*")
}

… just refuses to work: the file logback-test.xml is still there in the jar.
[1]: How to exclude src/main/resources files from the final WAR? - #2 by jjustinic

[Lance (uklance)]

First and foremost, test resources should go in src/test/resources then they won’t go in the jar.

Secondly, I think you need to remove the “resources” section from your exclude as this is the root folder, include / exclude patterns are relative to the root(s)

[mrodent (Mike Rodent)]

Thanks so much for answering so fast!