That won't do..."memory" refers to Derby's in-memory database, something
I put in to reduce the build time about 25% (instead of needing to
manually create files, etc.)...
I just use "mvn clean install", I don't have any problem on my machine
with it...
Glen
On 07/14/2013 04:21 PM, Dave wrote:
If I remove the string "memory:" from the two Roller property files in
test/src/resources then do not get that error and all test pass except for
the following:
Results :
Failed tests:
testUserLookups(org.apache.roller.weblogger.business.UserTest):
expected:<[userTest]User> but was:<[admin]User>
testRoleCRUD(org.apache.roller.weblogger.business.UserTest): expected:<2>
but was:<1>
Tests run: 130, Failures: 2, Errors: 0, Skipped: 0
Still digging...
- Dave
On Sun, Jul 14, 2013 at 4:11 PM, Dave <[email protected]> wrote:
I'm going to investigate now, but just in case anybody else knows what's
up...
--- ROOT CAUSE ---
java.sql.SQLNonTransientConnectionException: The connection was refused
because the database memory:rollerdb was not found.
at
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
Thanks,
Dave
