Skip to Content.
Sympa Menu

shibboleth-dev - Re: GridShib package names

Subject: Shibboleth Developers

List archive

Re: GridShib package names


Chronological Thread 
  • From: Mark Allen Earnest <>
  • To:
  • Subject: Re: GridShib package names
  • Date: Tue, 24 Jan 2006 10:02:03 -0500

For the lionshare plugin I took code from SAMLv1.1_AttributeQueryHandler.java (and attributed it as such) and basically kept the same package name except put it in psu's namepsace ( edu.internet2.middleware.shibboleth.idp.provider became edu.psu.middleware.shibboleth.idp.provider ).

One thing I did not do is put a license on it (although it has yet to be distributed), but I'm probably just going to keep the same Apache 2.0ish license terms for simplicity.

Mark Earnest

Scott Cantor wrote:
The GridShib plugin for Shib uses the following package names:

package edu.internet2.middleware.shibboleth.common;
package edu.internet2.middleware.shibboleth.common.provider;

For your code or referencing/incorporating other code?

Is this use of the edu.internet2 namespace "allowed"?

Not for code you're producing, no. Java packges are no different than any
other DNS-based hierarchy. It only works if people follow the rules.

If so, what
license header should be used in the source (both Globus and Internet2
derive from Apache License, Version 2.0)?

If you're copying in source from us, I would change the package names, but I
think the licensing terms let you do anything you want (including
relicensing it) as long as the "contains code from Internet2"
acknowledgement is present.

But under no circumstances should you drop the code in wholesale into your
jarfile. That's exactly what got Globus into trouble.

-- Scott

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.16.

Top of Page