v3 extensions

[Cantor, Scott]

On 7/2/14, 5:40 PM, "Jim Fox" <fox at washington.edu> wrote:

>To that end, is there somewhere an example pom.xml that I could work with
>to pull in the correct v3 idp jars?

There's no single short set of jars anymore because the projects are
multi-module.

I'm not sure if extensions would be using our parent POM directly or not.
That defines a lot of dependency versions and properties.

But the groupId coordinates for the new libraries are org.opensaml and
net.shibboleth.idp

There are a lot of modules and the artifactId dependencies will just
depend on what you're doing.

http://svn.shibboleth.net/view/java-opensaml/trunk/
http://svn.shibboleth.net/view/java-identity-provider/trunk/

Those are basically the module lists that would be dependencies in
different instances.

In most cases, looking at the POM for a module that would contain the
thing you're writing if it was part of the IdP would be a usual starting
point. So for a resolver plugin, idp-attribute-resolver-impl and/or
idp-attribute-resolver-spring are the examples to work from.

But the rule of thumb is that anything in -api is public and anything in
-impl isn't. So you shouldn't have any dependencies on -impl artifacts.

-- Scott