Refactor package names to match module names

[Cantor, Scott]

On 9/11/13 12:18 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>Most of the time, package names match their module names thus making
>it easy to identity the module that a fully-qualified class name is
>located in, for example, when working from a Spring configuration file
>to Java. There are some exceptions, and I would like to refactor :
>
>+ idp-core : net.shibboleth.idp -> net.shibboleth.idp.core
>
>+ idp-auth-api : n.s.idp.session -> n.s.idp.auth.session
>
>+ idp-profile-* : n.s.idp.relyingparty -> n.s.idp.profile.relyingparty
>
>+ spring-extensions : n.s.ext.spring -> n.s.spring.extensions
>
>Comments ?

Certainly in principle yes. I think the session stuff is going to want to
end up in its own module, but I'm not sure yet. For now I'd just leave it
until we have working code and I can adjust it then or as I work it out.

Also not sure about the relying party piece. Doesn't feel 100% like a
profile thing to me, at least not exclusively, but for now probably fine.

-- Scott