On 4/9/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
At the end of the link quoted below:
> a bridging api (which can reside within the same project - so can
be hosted at apache) >will be used to access these LGPL stuff to clearly
show its optional behaviour
This is probably the simplest thing to do. Make a bridging API that sits
at Mojo and the Apache plugin calls this bridging API. Moving the whole
plugin will cause total havoc on existing builds. (As would purging old
versions of it)
I fail to see how this works in practise. What license will have this
bridging API ?
J
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
