Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I have used two tools while working on JParser, they are ANTLR(1) and
the ANTLR Eclipse Plugin (2). The first is public domain code (under
no particular license) and the second is released under the CPL.
It happens that the generated parser code has a runtime dependency
with the antlr library. This boils down to we needing to have the
antlr.jar library at runtime, which takes us to the real issue: how
should we make this library available?
I have thought of three choices:
- The first is to package the library directly inside our plugin(s).
There are no legal restrictions to that, since the antlr jar is public
domain, but it doesn't seem right to bundle library code directly
alongside our own code.
- The other is to depend on the antlr plugin and have it provide the
library. I don't know if there are legal restrictions here, since the
plugin is released under CPL and I really don't know it. But there is
on technical drawback that is the library code comes together with
plugin code that users don't necessarily need. This will consume
unnecessary storage and can lead to plugin interaction issues.
- The last one (very similar to the second one) is to make (or find --
maybe the one from the antlr plugin itself) an antlr plugin that will
only provide the needed jar (just like the org.junit plugin).
I would like to listen to your opinion on that.
(1) ANTLR Parser Generator - http://www.antlr.org/
(2) ANTLR plugin for Eclipse - http://antlreclipse.sourceforge.net/