--- Conor MacNeill <[EMAIL PROTECTED]> wrote: > Morgan Delagrange wrote: > > OK, Java-specific question. It seems likely that > > altering or inlining LGPL code pollutes the Apache > > license. Are you of the opinion that IMPORTING > but > > not altering or distributing LGPL classes pollutes > the > > Apache licecnse? And if so, can that be stated on > the > > Wiki page? If LGPL code cannot be imported, it's > > pretty much useless in any capacity for Java > projects. > > > > Refer to Roy's messages of yesterday. Importing is > enough to disallow the > code from use within ASF code. > > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1419 > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1429 > > > Conor >
Good enough. Section 6 does seem pretty damn rigid. I thought we might have covered imports specifically, but I had already deleted yesterday's mail. Dang, I wish that archive was searchable. [wink, wink] Ken, can we get this on the Wiki page to protect feeble-minded folks like me? http://nagoya.apache.org/wiki/apachewiki.cgi?Licensing - Morgan ===== Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
