On 6 February 2012 14:43, Mladen Turk <mt...@apache.org> wrote: > On 02/06/2012 12:48 PM, sebb wrote: >> >> On 6 February 2012 10:12, Mladen Turk<mt...@apache.org> wrote: >>> >>> On 02/06/2012 09:30 AM, Mladen Turk wrote: >>>> >>>> >>>> >>>> Is there anything else we should consider before doing that? >> >> >> I've just raised DAEMON-240; it would be good if the docs could be >> updated accordingly. >> > > Sure, but the docs can always be updated at any time. > We don't have to wait for a release or something to update our web site.
That particular JIRA could involve code changes as well. Also, we include the site source in the archive. > Think we should create a separate component 'documentation' > and handle that separately from code itself since it belongs to src/site Perhaps. However, we should also consider including at least some of the generated documentation with the binary archive. Updating the site is all well and good, but it will in general not correspond to an existing release, as I would expect the site docs to be updated with changes to the source. > > >> Also, is it possible to resolve DAEMON-234 easily, or will that take a >> lot of work? >> > > Done. libcap is now dynamically loaded and there is no more > buil-time dependency on libcap.so.X > > > > Regards > -- > ^TM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
