Thanks. I examined those instructions in greater detail, and reviewed
all the dependencies we bundle, and I think I was able to cut a lot of
bloat out of LICENSE.
JCommander is weird, because it contains a notice.md file in its
source, that it looks like we're supposed to include, but it probably
didn't really need to do that to begin with. Oh well. Aside from that,
it didn't look like there were any other NOTICE contents to carry
The link also showed how pointers were okay. However... there's a
separate thing to do for jline, because we bundle it only in our
binary distribution (nothing to point to), so I just left the license
in, with a note that it applies to our binary packaging. To improve
this, we may want to automate the generation of the LICENSE file to
include in the binary packages.
Christopher L Tubbs II
On Thu, May 16, 2013 at 3:16 PM, Billie Rinaldi
<[EMAIL PROTECTED]> wrote:
> In case it isn't:
> billie: here are the instructions:
> billie: it seems to imply that only ALv2-licensed code that has a NOTICE
> file needs to be propagated to our NOTICE
> billie: does that mean we can just take other ALv2-licensed stuff out of our
> LICENSE file?
> billie: also, i was wondering if we need to do something like this: