I have a application.dev.conf
and application.test.conf
under my conf
folder in my Play 2.3 application but I do not want it to be packaged as part of my distribution? What is the right excludeFilter
for it?
相关问题
- Unusual use of the new keyword
- Get Runtime Type picked by implicit evidence
- What's the point of nonfinal singleton objects
- PlayFramework: how to transform each element of a
- Error in Scala Compiler: java.lang.AssertionError:
相关文章
- Gatling拓展插件开发,check(bodyString.saveAs("key"))怎么实现
- RDF libraries for Scala [closed]
- Why is my Dispatching on Actors scaled down in Akk
- How do you run cucumber with Scala 2.11 and sbt 0.
- GRPC: make high-throughput client in Java/Scala
- Setting up multiple test folders in a SBT project
- Testing request with CSRF Token in Play framework
- Run project with java options via sbt
Actually lpiepiora's answer will do the trick, however note that filtering on
mappings in Universal
will only excludeapplication.dev.conf
from theconf
folder and NOT from the jar itself.I don't know about the
play
framework but in general if you have something like this:Doing:
would produce the following package structure:
However if you look into the jar, you will see that your
dev.conf
file is still in there:This is actually not really harmful but if you want to remove them too, here is the answer: How to exclude resources during packaging with SBT but not during testing
You could use
mappings
to exclude both files.Does an
excludeFilter
as follows work for you?(The
unmanagedResourceDirectories
key refers toconf/
by default.)