On Mon, Mar 5, 2012 at 2:34 PM, Mattmann, Chris A (388J) <[email protected]> wrote: > Hey Ryan, > > On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote: > >>> >>> Unfortunately I do see it as a roadblock. The goal of SIS was to write >>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which >>> in my mind does *not* include any dependencies (even optional) on >>> LGPL components. >>> >> >> Got it, this was my understanding. The goal of SIS is to build an ASL >> version of JTS -- that's a great goal, just not one I have any >> energy/time to contribute towards. > > No worries. I appreciate you reaching out. Is there a way to have everything > in spatial4j that doesn't rely on the LGPL code here? >
possible, but it makes testing overly complicated. I want/need the JTS implementations to be 1st class test citizens. (This is actually the biggest reason this is not directly in the lucene) >> >> >>> Is there any way that the works of spatial4j could be replaced by ALv2 code? >> >> The code in spatial4j is all ASL. If there were a viable ASL polygon >> library, we could use that too. > > How can you have an ALv2 licensed library that has dependencies on LGPL > upstream > components? Doesn't the LGPL and its viral nature [1] spill into your code? > You may be confusing LGPL with GPL. "Applications which link to LGPL libraries need not be released under the LGPL" http://www.gnu.org/licenses/lgpl-java.html The key thing they want to make sure is that you don't bundle your own version of the .jar file (section 6)
