I just pulled the latest code from Trunk this morning. I ran the unit
tests in ./core and had the following result...
2007-11-03 21:11:26,437 INFO net.sf.ehcache.CacheManager - VM shutting
down with the CacheManager st
ill active. Calling shutdown.
Exception in thread "Thread-77" java.lang.Illegal
What tests are failing? And what platform are you running on, JVM, Maven
version etc?
The stuff about ehcache is something to do with the shutdown hooks in
all the application contexts being executed when the VM exits so that's
not the problem, though we should be aiming to make sure that existing
Maven version: 2.0.7
Java version: 1.6.0_01
OS name: "windows xp" version: "5.1" arch: "x86"
Yeah, the console scrolled way too far back for me to see what failed.
That was just the snippet of the end of the log I showed.
I'm running it again with a fresh batch of code, and running it from
the pr
This type of stuff seems to be where it takes the longest...
2007-11-04 12:39:38,062 DEBUG
org.springframework.security.ldap.DefaultInitialDirContextFactory - Cr
eating InitialDirContext with environment
{java.naming.provider.url=ldap://127.0.0.1:3389/dc=springf
ramework,dc=org,
java.naming.factor
It looks like that all starts from this test...
Running
org.springframework.security.providers.ldap.authenticator.PasswordComparisonAuthenticatorTests
On 11/4/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> This type of stuff seems to be where it takes the longest...
>
> 2007-11-04 12:39:38,062 DEB
Ok, so this is a Windows and/or Java 6 thing.
I ran the full test suite on my linux box with java5 and all is well.
On 11/4/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> It looks like that all starts from this test...
>
> Running
> org.springframework.security.providers.ldap.authenticator.Passw
I found the problem!
In the LdapBeanDefinitionParser I see this...
//TODO: Allow port configuration
configuration.setLdapPort(3389);
The TODO says it all :), the problem is that 3389 is the port that
Windows runs the Remote Desktop service on. I figured this out because
I saw "po
Great. Thanks for working this out, Ray.
I've added support for setting the port via the namespace, but
we'll still need a default port value, so I've switched it to 33389. The
tests now use 53389 (by setting the port attribute) which is in the
dynamic port range (http://www.iana.org/assignments/p
