Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of phidias51@gmail.com
 designates 209.85.134.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=mb9Ui197DI0E3hEfoP4kF9XYGfFhpDZyM3oBhE6ZgP+WFF4Z9QoG9GofBSLa4erIYclIw/2SuNuC8U2pMu6i75GLXLhHkkLHonElX7ohCQaxsXOuhmOmRm3Xeo6IVk2CUsmh2Zw9V3d4ft/fLLxR4F4RkTBIKdj612RaYEwplMo=
Message-ID: <6e1d61f50708192213r27d4cf77h3186a5d5133d13b0@mail.gmail.com>
Date: Sun, 19 Aug 2007 22:13:55 -0700
From: "Mark Fortner" <phidias51@gmail.com>
To: user@commons.apache.org
Subject: [all] Standardized Manifest For Commons JARs
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_103538_5843891.1187586835426"

------=_Part_103538_5843891.1187586835426
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've been working on a project to help catalog the JARs that we use and the
concomitant licenses that they employ so that we can more easily comply with
sections 4a and 4c of the APL without having to do a lot work to compile the
license information.  I thought at first this would be fairly simple to do,
given that all of the Commons projects (that we use) have manifests.
However, I soon discovered that the manifests have a variety of different
attributes and aren't really standardized.

I was wondering if it would be possible in the next release(s) if the leads
for the projects could modify the manifests (or the ant/maven builds that
generated them) to include the following information:

License Type: APL
License Version: 2.0
License URL: http://www.apache.org/licenses/LICENSE-2.0.txt

or

License URL: /license.txt
if you've included the license file in the jar file.

This would help us insure that we're providing the appropriate license
information when distributing Apache libraries with our code.

Regards,

Mark Fortner

------=_Part_103538_5843891.1187586835426--