Shibboleth Developers

[Tom Scavo <>]

On 8/23/05, Tom Scavo 
<>
 wrote:
> An extension stores source and other resources on the classpath in
> directories src and src-conf, respectively.  Similarly, does it make
> sense to have tests-conf in addition to tests?  Without it, I don't
> know how to test classes that expect resources on the classpath.  Any
> suggestions?

I found a workaround.  I have the following resource in my extension:

src-conf/conf/gridshib-idp-config.properties

This resource gets copied to

build/tests/conf

as it should, but the placeholders are not replaced.  To workaround
this, I created another resource

src-conf/conf/test-gridshib-idp-config.properties

with the placeholders replaced with reasonable values.  Now when the
JUnit test runs, I tell it to look for
test-gridshib-idp-config.properties (instead of
gridshib-idp-config.properties) on the classpath, which works since
${ext.classes} is on the test classpath.

I had to create a bit of machinery to allow arbitrary config files,
but it works.  On the other hand, test-gridshib-idp-config.properties
is bundled in the JAR, which doesn't cause any serious problems as far
as I can tell, but it would be better if it weren't in the extension
JAR.  So my question is:

Can replaced versions of all resources in src-conf be made available
to the test framework?

Thanks,
Tom