Strange local behavior running some of the idp-config tests

[Rod Widdowson]

For some time now some of the tests for idp-config have been failing for me.

I had a some time today to dig into this some more and the tests always fail
because they cannot find the flow "access/attr-check".

Looking at this in the debugger, AFAICS none of the flows defined under
"conf\flows" are being registered, however when I run inside
java-idp-testbed they are.  Demonstrably when Jenkins runs these tests these
sub flows are being found.

After a fair bit of poking around it turns out that inside
org.springframework.webflow.config.FlowDefinitionResourceFactory the field
basepath is initialized to be

C:\Perforce\Juno\New\java-identity-provider\idp-conf\src\main\resources/flow
s

For the test case and 

C:/Perforce/Juno/New/java-identity-provider/idp-conf/src/main/resources/flow
s

In the idp-testbed case.

Obviously when that code goes to strip off the common header from a path
like

C:/Perforce/Juno/New/java-identity-provider/idp-conf/src/main/resources/flow
s/access/attr-check

Things go pear shaped and we end up registering a flow called 

"C:\Perforce\Juno\New\java-identity-provider\idp-conf\src\main\resources/flo
ws flows/access/attr-check"

I'm hoping that Tom, having spent that delightful time (that's irony)
working out how idp.home works will be able to tell me what we need to add
to the test framework inside idp-config to make this work...

Right now I'm not blocked on this because I'm not dependant on the flows,
but it’s a pain to not be able to run 'mvn install' to completion (my aim in
fact is to run 'mvn site' and take a quick look at the code coverage).

/R