Test mode resources

[Phuong Nguyen]

I have specify my database name in "cx.properties" and put it in "src/
main/resources/"
The problem is during test mode, I need to drop all tables in the
database. I'd like to leave the development database safe by putting
another "cx.properties" in "src/test/resources". However, such
solution works sometime and not the other time. Right now, I switch to
another machine (Ubuntu 10.10) and it doesn't work: My development
database tables dropped everytime I run the test.
Is there any specific things that I should notice when trying to
override some settings during test mode?

[Mark Harrah]

It is better not to rely on classpath ordering. Remove any paths from the classpath that you don't need, such as src/main/resources/cx.properties.

override def testResources = super.testResources --- (mainResourcesPath / "cx.properties")

-Mark

[Jem]

I consider this tactic (overwriting prod-time config with test-time variants) as pretty standard. Why shouldn't SBT ensure test resources are always preceding the standard resources?

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

[Gustavo Hexsel]

  I agree, to me this is a bug.  We use it all the time in Maven, there are a dozen spring files, but you want to overwrite the one with the database config or the email server or such.

[drwho]

test resources should definitely go before standard resources — was a bit surprised to learn that sbt is not doing that.

[Alon Lavi]

Hi,
Do somebody know if it is solved in the latest versions?