On 1/9/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Adam Lally wrote:
> On 1/9/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
>> Being that we're copying what other Apache projects do here with regard
>> to 3rd party JARs, I don't think we have to
>> be concerned, beyond what the README-FIRST does.
>>
>
> Where exactly did you get this stuff from?

It's from their SVN:
http://svn.apache.org/repos/asf/velocity/docbook/trunk/ etc

It's not "distributed" - e.g. it isn't put into a "build".  (By "it", I
mean the docbook
stuff needed to build from docbook sources -> html / pdf).


I can't even find their final build html / pdf documentation anywhere,
even on their website.  As far as I can tell the things in
velocity/docbook/trunk are not being used for anything.

I downloaded a velocity engine source distribution, and it contains
xdocs files (from SVN under velocity/engine/trunk/xdocs), from which
you can build html.  But these don't seem to have anything to do with
what's in SVN under velocity/docbook/trunk.  So that didn't really
help give us a model for what we should do.

I think we're agreed that the docbooks sources should be in the UIMA
source distribution.  The question then is what do do about building
it.  It seems our choices are:
(a) Include all the jars in SVN as part of our source distribution.
The licenses all seem OK, but we will need to update our NOTICE file,
for our source release only.
(b) Do not include any of the jars.  Require that users get them from
our SVN, instead.  I guess that means we wouldn't have to do anything
with our NOTICE file. (But IANAL.)

Which should we do?

-Adam

Reply via email to