Just tried to use the new tests for the API and received the following error.
rc\test\resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [scala:testCompile {execution: default}]
[INFO] suggestion: remove the
You can try and change the object name to JettyTestServerAPI but
then you get a strange DB error.
I tried work arounds but didn't get very far.
Ideally, we just use the same Jetty object for the tests. Maybe tests
could have the option of reusing an existing database or creating a
new one.
I thought that might be a problem, but for some reason it didn't error
on my build. I'll try to refactor the tests so that they can use the
same JettyTestServer object.
Vassil, does that sound like the right approach to you?
It's definitely better to use the same JettyTestServer. Not only is
On Sun, Nov 8, 2009 at 10:50 PM, Anne Kathrine Petterøe
akpette...@gmail.com wrote:
Excellent, thank you Dick.
The designer has started turning the templates into HTML/CSS now as well.
* Do we want the ability to filter by pool on the main message page?
Or is this just on the Streams
