On 08/15/11 02:32, Marshall Schor wrote:
yes, it's entirely manual at the moment.
-Marshall
On 8/13/2011 10:30 AM, Stefan Bodewig wrote:
On 2011-08-08, Marshall Schor wrote:
We recently did an exercise whereby for some projects for which we
distribute binaries that include "dependencies", we looked inside the
dependency Jars being distributed to see if there was any unusual
license and notice (and other) files, and we found several; we then
manually merged these into the binary distribution's License and
Notice files.
I assume this has been some sort of manual process, right? Or is there
already anything that could be the seed for some tooling?
Assembling applications consumed by end users and composed from numerous
component libraries is the use case which led to me to Whisker. Apache
James 3.0 contains over 150 libraries. Manually maintaining correct
LICENSE, CRYPTO and NOTICE documents is error prone and time consuming.
Whisker currently uses an XML document to store licensing data matching
license meta-data to artifacts. In generative mode, velocity templates
are used to generate LICENSE and NOTICE documents. In validation mode,
the meta-data is checked against the contents.
So, Whisker could help with maintenance but not discovery.
Robert
