Shibboleth Developers

[Tom Scavo <>]

On 5/31/05, Walter Hoehn 
<>
 wrote:
> 
> The 1.3 IdP and SP will not be released on the same schedule
> and we want to retain the flexibility to cut a point release for one
> without rev'ing the other. 

Sure, I understand what you want to do.  If you modify something in
the idp package, for instance, you release a new version of the IdP. 
The problem is the shared code (common, log, metadata, xml).  If you
modify any of this core code, you modify both components by
definition.  Doesn't matter if they live in the same webapp context or
not.

> This is the main motivation behind
> separate packages, even though they will contain mostly the same stuff.

Seems like mainly a cosmetic distinction.  Since they share code, they
are dependent upon one another despite the apparent separation into
two distinct webapp contexts.

I really don't see how this is going to work without some additional
structure.  From my vantage point (as a developer working off CVS
HEAD), investing additional time in the Java SP is a somewhat risky
proposition.

Tom