Shibboleth Developers

["Scott Cantor" <>]

> Like shib-util.jar? :-)

Seems like something worth fixing to me, although this isn't an extension,
it's the entire source tree. It's not unreasonable to imagine wanting to
have multiple versions of an extension in use at once if the classes didn't
conflict, but that's not reasonable for this jar.

> Unless I'm mistaken, this will lead to multiple jar files in
$IDP_HOME$/lib:
> 
> lib/gridshib-idp-0.3.jar
> lib/gridshib-idp-0.3.1.jar
> lib/gridshib-idp-0.4.jar
> etc.
> 
> This would be bad, right?  Am I missing something?

An upgrade process, I guess. We can't assume everybody is versioning their
stuff like this, so that means people need to clean up old extensions
somehow. Seems like that would be true unless you *assumed* the jar was
always named the same, and that's an equally bad assumption, IMHO.

What about other cases where an extension had its own supplementary lib
files that *did* have the version in the name, and the new extension uses a
newer version? Actually, this is true across extensions, which is even
worse.

I already think we've gone way farther in the build/install arena than was
expected, and way beyond what any other Java application seems to support.
It's a slippery slope, and now we're sliding.

Personally I would have been satisfied if extensions didn't install
themselves, which is what I said originally. I just wanted to be able to
customize the warfile build and factor out the configuration, and that's it.

-- Scott