The LICENSE and NOTICE files can be tided up. They were setup so
individual modules can be released by themselves but Jena now releases
all modules at once.
So the L&N can be reduced to:
* One (of each) in the root of the source repo.
* One per distribution binary where the binary includes things not in
the repo (but linked to by maven).
* One in each jar. The automatically generated one probably isn't good
enough. What I don't know is whether it can be the top-level one or per
module (which does rather infer with the tidying up exercise).
Dist areas:
+ apache-jena/dist
+ apache-jena-osgi/dist
+ jena-fuseki2/apache-jena-fuseki/dist/
+ jena-fuseki1/dist/
We could drop the Fuseki1 distribution and just make the server jar. It
needs L&N to reflect the included dependencies.
Consequences:
* Javascript means source in the repo so all the MIT license refs need
mentioning in the top level.
Andy
JENA-1572 has my assessment of all the current L&N files.
JENA-1571 removes the dist/ and assembly for jena-sdb.
