[mystikal]

I'm also fine if you pull out bits of my code and use them in your codebase, just as long as you release the changes to those bits. Probably function-level granularity for separating mine from yours would work, and I don't expect you to write wrappers. Also automatically doing stuff with my code is fine.

[geofft]

I'd expect that counts as modifying your library (to remove all but the lines of code I want to use), at which point I can avail myself of the classpath exception by being GPL-compliant for just those lines of code -- offering the complete corresponding source in the preferred form of modification.

[mystikal]

I think you still have to ship it in a separate tree / binary, but I'm not sure. I don't think the exception means you can put my GPL function in your proprietary code and call it as long as you reveal the changes to my function. But I'm willing to settle for "who knows, really" :)

I worked a bit on Classpath but that was a long time ago. There are like, lots and lots of emails + irc logs to dig up about that little exception and what it means. Not having things tested in court is a problem, and the lack of funding for FSF lawyers is another.