Thanks for your reply. That's probably what I'll end up doing... For some reason, all the documentation and questions seem to assume the config file should be a resource, so I just went with that.
On Tuesday, April 14, 2015 at 7:15:17 PM UTC+3, Adam wrote: > > First of all, regardless of inclusion, you need your build to exclude this > application.conf file from jars. There's not much point for a configuration > file that can't be easily modified. It should instead be in a folder (e.g. > ./conf) that is added to your classpath. > > Then, you can either add your own file with an include directive for > application.conf and load your file as the main one via the system > property, or you can have your build rename the original application.conf > (e.g. to some-lib.conf) and name your file application.conf and again use > the include directive with the name you picked. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
