| > The problem, AFAIU, is that this Maven's code now has to become LGPL licensed | > itself, due to LGPL license requirements. And ASF repositories can't contain | > LGPL code. So the answer is to pull (quickly) this code from Maven, and not to | > introduce to Slide. | | Incorrect. Unless maven core depends on LPGL, which afaik doesn't. | Just the plugins that depend on LGPL code need to become LPGL and | probably need to move. | The plugin architecture prevents the core from becoming "infected".
I believe this is untrue. LGPL doesn't infect, as such. It just places restrictions on how much you can restrict your users/customers of your code with your own license. I think that the problem is that -if- you have LGPL code in your system, then you must accept that the code using the LGPL code can be traced, disassembled and analyzed (and possibly packaged in such a way that the borders between your code and the library are clearly defined). The reason for this, is that a user shall have the option to -replace- the library with another version, or another implementation, and shall thus not be restricted from analyzing exactly how your code is using it. I might be dead wrong. Endre --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
