On Fri, 13 Feb 2015, Allison, Timothy B. wrote:
For your suggestion:
(Actually, there's nothing stopping someone publishing an "all Tika
including LGPL" or "all Tika including GPL" pom, which auto-includes
these for those users who can use things under those licenses in their
projects, but for policy reasons it couldn't be a PMC action to publish
that)
It would be more than just the pom, though. It would have to be a
separate project that included the Tika parsers that wrapped these
non-ASL libraries, or do I misunderstand? Oh, wait, are you suggesting:
Step 1) create the Tika wrapper parser as a standalone project, Step 2)
publish the L?GPL poms to include both the Tika parsers and their
dependencies?
I'd see it as two steps:
1) Ensure that all the parsers on the 3rd party page have a suitable
published pom, including their dependencies
2) Create new projects (on github etc) as "tika-parser-with-lgpl" and
"tika-parsers-with-lgpl-gpl", which are a pom that depends on
"tika-pasers" and all the gpl and/or lgpl parsers, and a simple unit
test which ensures those parsers were registered + work
Step #2 looks pretty easy, step #1 might be more work as we'd have to get
those parsers released, get their dependencies into maven central etc.
With that work done though, someone who was willing+able to use LGPL
plugins would switch their maven dependency from "org.apache.tika" +
"tika-parsers" to "net.github.tika-extras" + "tika-parsers-with-lgpl"
Since we don't need to offer downloads, just code, Apache Extras might be
possible for hosting the wrapper-pom + unit tests, but it might be that
github would be simpler
If we do want to do this, and if someone's willing to do the work, it
might be best to double-check with legal-discuss to make sure we haven't
missed anything first!
Nick
