Stuart Turton - 2013-01-03

The referenced libraries and their associated licences are described in http://pldoc.sourceforge.net/maven-site/dependencies.html, which is generated automatically.

These libraries have always been used to compile PLDoc - with the move to Maven and the creation of generated PLDoc distributions, their classes are now included in some JAR files.

I infer from a quick reading of http://www.apache.org/licenses/LICENSE-2.0.txt that:-
the plain pldoc*.jar are not derivative works (they do not contain the Apache classes) and so no licence information is required;
the pldoc*-with-dependencies.jar _ARE_ derivative works and we should be including a copy of the Apache 2.0 licence.

A quick unzip shows that the with-dependencies JAR file contains the original licence information (5 files) and a NOTICE file - all referring to the Apache code (see below) - this I think compiles with 4(d) of the licence.

" =========================================================================
== NOTICE file corresponding to section 4(d) of the Apache License, ==
== Version 2.0, in this case for the Apache xml-commons xml-apis ==
== distribution. ==
=========================================================================

Apache XML Commons XML APIs
Copyright 2006 The Apache Software Foundation.

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

Portions of this software were originally based on the following:
- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
- software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
- software copyright (c) 2000 World Wide Web Consortium, http://www.w3.org
"

The wording in our ReadMe.txt (see below) is very similar to that in Apache's own NOTICE file
"
This product includes software developed by the Apache Software Foundation:
http://www.apache.org
See file xalan/license for information on redistribution.
"

I will check with Apache whether they think that keeping all of their licence/notice within the consolidated JAR file meets their interpretation of the Apache 2 requirements.