Closed GoogleCodeExporter closed 9 years ago
I can't remember where I got the Java Lexer :-( It could be GPL.
But I'm working on a better Java / Groovy Lexer that will support better styles
for
JavaDoc style comments, and Groovy GStrings, so the Java and Groovy lexers will
be
re-written, and will be Apache 2.0
Original comment by ayman.al...@gmail.com
on 7 Sep 2008 at 6:54
That is bad news :( . GPL has strong copyleft
(http://en.wikipedia.org/wiki/Copyleft)
and doesn't allow linking from a different license. That might mean that the
jsyntaxpane project needs to be GPL until you replace the lexer. You should
definitely place a warning on the front page.
Do you plan on fixing this soon? I can't use the project if it contains GPL
code.
Original comment by javlo...@gmail.com
on 7 Sep 2008 at 6:13
It could take me few days or even a week or so... it all depends on the work
load at
my day job :(
I'll work on this issue as the highest priority thing to sort out. Including
this
file without paying much attention is a mistake, and not intentional.
However the probable root of the source is jflex itself, and the license for
jflex
clearly says the generated code is not copyrighted...
Original comment by ayman.al...@gmail.com
on 7 Sep 2008 at 6:35
The jflex license says generated code inherits the license of its source. So if
java.flex is GPL then JavaLexer is also :(
Thanks for making it a priority.
Original comment by javlo...@gmail.com
on 7 Sep 2008 at 11:04
The JFlex front page has this:
"Yes. It is released under the GPL and available for free download. See also
Copyright, License & Warranty. Code you generate with JFlex is not covered by
the
GPL, it is yours. "
If that was not the case, we could not even use JFlex to release any version.
Original comment by ayman.al...@gmail.com
on 8 Sep 2008 at 6:53
Yes, so the only problem right now is with java.flex. Once we clear that up
there
will be no more licensing concerns.
Original comment by javlo...@gmail.com
on 8 Sep 2008 at 4:45
New lexers are implemented.
Original comment by ayman.al...@gmail.com
on 21 Sep 2008 at 12:30
Original issue reported on code.google.com by
javlo...@gmail.com
on 4 Sep 2008 at 5:30