Any more info on this, as I am potentially in a similar position if I go ahead and use some lgpl jars?
The clearest explanation of java.lgpl issue I have found is http://www.gnu.org/licenses/lgpl-java.html
So I can produce an executable with Jet that still dynamically links the jars at run time, from say a lib directory?
Jet will allow me to do this? ["Mixed Compilation Model" I think?]
[ and then I just have to include source of the lgpl jars as well as copyright notices]
I think the reverse engineering clause that is standard in most licenses you would not have due to the lgpl reversere engineering provision, but in reality people will do it anyway so having a combo of obfuscation and jet I guess will make it a little tricky for them. http://www.javalobby.org/forums/thread.jspa?threadID=15903 has some interesting conversation on the reverse engineering issues.
or am I reading it wrong?
By Object code do you mean my app .class files before they go through Jet?