IdPv3 idp-war Maven Artifact

[Marvin Addison]

> One of the undone areas of work that may not even make 3.0 is formalizing
> extension installation. It's possible you might be able to propose some
> ways that might work.

Maven War overlay definitely has worked well for us in the CAS
project. It allows one to focus on only the components that need to be
added or changed. Specifying additional dependencies, components, and
configuration as well as config tweaks is straightforward. The only
downside is that it's clearly suited to developers, which can create
some unease with sysadmin-type deployers.

I intend to use it, at least initially, for CAS extension integration,
so hopefully that case will identify benefits and liabilities
generally.

> I think one of the reasons for moving away from custom bean schemas is
> probably to facilitate injection of extensions in a more Spring like way.

I would think so, yes. I understand the need to provide backward
compatibility with existing configuration, but supporting straight
Spring as a new configuration method generally would make a number of
configuration tasks more natural for those of us that are already
familiar with Spring.

M