Thanks Steve. For clarity: This message announces a license switch for Greenmail -- http://sourceforge.net/p/greenmail/mailman/message/58953/ However, some/most/all of the src license headers are still labeled as LGPL. There would also be general questions about the license switch -- were all necessary copyrights properly held to make this license switch? And subsequent to the switch were all changes/contributions made under ALv2?
Depending on the outcome of these questions, you may or may not want to treat the greenmail dependency as LGPL. Assuming it is held to be LGPL, then a question of how the dependency is used? Bundling an LGPL dependency is bad. Direct source linkage to LGPL, likewise. Simple build / test maven dependency would be OK from an ASF perspective... On Sat, Jul 12, 2014 at 12:36 PM, Steve Rowe <sar...@gmail.com> wrote: > Hi, my name is Steve Rowe, and I'm a member of the Apache Lucene PMC. > > We recently discovered that the "greenmail" Java library, which declares > its license as ASLv2 in its POM and elsewhere, has LGPL license headers in > its source code files. In response the Lucene project reverted a recent > commit containing this depedency. > > I conducted a survey of current Apache releases and found that four Apache > projects include source code that links to the "greenmail" library: > Syncope, OODT, Oozie and Geronimo. Additionally, Axis2 has a Maven POM > that includes a "greenmail" dependency, though I couldn't find any current > releases containing this dependency. Details are posted on < > https://issues.apache.org/jira/browse/LEGAL-206>; I would appreciate your > project's involvement. > > An issue was filed with the greenmail project on Sourceforge earlier this > year asking for clarification <http://sourceforge.net/p/greenmail/bugs/8/>, > but there has been no response on that issue, or any other issue, for that > matter - the project may be dead, as it has seen no activity for some time. > > Steve >
