JBoss Queries Apache Geronimo Code Similarity
Kanagawa writes "This morning, Jim Jagielski, Exec. V.P. and Secretary of the Apache Software Foundation, announced on the geronimo-dev mailing list that 'the ASF received a letter from JBoss's lawyers regarding... the similarity of code between [J2EE implementation] Geronimo and JBoss.' The letter
is available in PDF. According to the letter, similarities were noticed back in July, and haven't been fixed."
That's exactly the problem. Geronimo is a project of the Apache Software Foundation and as such must be licensed under the ASF license. LGPL code cannont arbitrarily be relicensed.
The first example in the letter is
org.jboss.logging.XLevel vs. org.apache.geronimo.core.log.XLevel
Both seem to be copied from log4j's examples.customLevel.XLevel
However, there are much more substantial allegations made here
more about me
No mystery there. ThreadNDCConverter is capitalized *exactly* according to very established java code conventions. See for example http://java.sun.com/docs/codeconv/html/CodeConvent ions.doc8.html
The JBoss code and the Apache code both appear to be copied from an example that was originally created by Apache. Exibit A and B are both logging classes, both use Log4J (Apache's logging utility) and can be expected to be similar. Exibit C looks Almost identical, but not entirely. The similarities are so trivial, Apache is bound to make a few quick changes and be done with this thing before it starts. What sillyness.
TallGreen CMS hosting
JBoss has noticed similarities and has raised the issue (a second time) with Geronimo.
Minor nit: This is actually the first time this was raised directly. Early on, the ASF was contacted by JBoss simply to "remind" us that JBoss is covered under GPL and that any derived code could not be relicensed (under the Apache License). At the time, no real work on Geronimo had been done so that there was no actual code that could be shown to be similar. The above leaves the impression that the ASF had ignored a previous notice from JBoss, which is certainly not the case.