river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Brouwer <mark.brou...@cheiron.org>
Subject Re: [jira] Created: (RIVER-269) build reports problem with javadoc generation on Windows
Date Tue, 09 Oct 2007 20:48:42 GMT
Frank Barnaby wrote:
> 
> On Oct 9, 2007, at 2:33 PM, Mark Brouwer wrote:
> 
>> Mark Brouwer (JIRA) wrote:
>>> build reports problem with javadoc generation on Windows
>>> --------------------------------------------------------
>>
>> As discussed in 
>> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200705.mbox/%3c465AEAC5.7020508@cheiron.org%3e

>> I'm modifying the footer of the generated javadoc. Below you find my 
>> current idea, feel free to comment.
>>
>> Copyright 2007, multiple authors.
>> Licensed under the Apache License, Version 2.0, see the NOTICE file for
>> attributions.
>>
>> 'Apache License, Version 2.0' is a link to the official license and
>> 'NOTICE' is a link to the NOTICE file that is being copied to a
>> doc-files directory.
> 
> 
> The NOTICE file currently resides in the top level of the distribution.
> Are you suggesting that it be relocated or copied to the doc directory?

Hi Frank,

As part of the doc target I added this:

     ...
     </javadoc>

     <mkdir dir="${build.doc.api}/doc-files"/>
     <copy file="${build}/NOTICE"
            tofile="${build.doc.api}/doc-files/NOTICE"/>

   </target>

Effectively this will copy the NOTICE file into the javadoc tree, and I
refer to the copied NOTICE file from the footer. No relocation takes
place, just a way to be able to use the javadoc standalone.
-- 
Mark

Mime
View raw message