Unexpected consumption of env.yml.tmp during mvn package tests

[Rillke]

When running mvn package, env.yml.tmp and server.yml.tmp are consumed instead of those without .tpl extension. This is undocumented and unexpted. Tests fail if no mongodb is running on localhost and on the other hand, if a mongodb is running at localhost it is accessed during mvn package, which might be unwanted or unexpected.

The official deployment manual says:

Copy the included configuration env templates for both the server and UI repos

and later

Package the application using Maven

However, it fails to mention that hard coded test.

[abyrd]

Hello, I believe these tests (and the build as a whole) are only really configured for our continuous integration environment. That's the only way the project is ever built in our usual process. Point taken though, if people are going to be building this in other places we need to make it clear that the tests connect to the DB and adjust the config files so that's even possible. We might somehow put those database-backed tests into an optional profile.

[abyrd]

@landonreed do we have any necessary tests that need to connect to either database? Why does this particular test use one configuration file that does not exist (server.yml) and another configuration file that doesn't seem to provide enough information to connect to Mongo? How does it work within the CI environment?

[abyrd]

Ah, I see we've got a line in the Travis config that does cp configurations/default/server.yml.tmp configurations/default/server.yml. I would say the build and tests should run out of the box with as little prep as possible. Maybe we should have a configurations/testing containing the appropriate configuration files.