http://www.noodleheaven.net/JavaOSG/javaosg.html
http://www.noodleglue.org/noodleglue/noodleglue.html
I just popped to JavaOSG site, anyone has experience how it works?
Too restrictive license for most of us… GPL
:-X
I have tried NoodleGlue before in an attempt to wrap an old project of mine, but the code that is generated by it is…different. It also required you to package the glue jar along with the application and since it is LGPL, it just wouldn’t work…
However, im sure with some tweaking to the config files, it’l work a treat…
DP
Lifted from the NoodleGlue site:
“I should probably point out what may be a common misunderstanding about the licensing here - the code that NoodleGlue produces is your own - you can do what you want with it, so licensing is only really an issue if you wanted to do something like embed NoodleGlue itself into something like an IDE (… which would be cool, is someone felt like doing it …).”
Basically, we want people to be able to use NoodleGlue for any project, regardless of license. However, if improvements are made to the wrapper generation code, we’d like those improvements to be made available to everyone.
The noodle glue runtime (which must be linked into the finished app) is released under the LGPL. Our intention was that anyone could use noodleglue for any application and that only changes to the runtime source files should be made available to everyone. I realise that LGPL is probably not the most appropriate license (being too restrictive in my opinion). We don’t really want users to have to dynamically link to the noodleglue C++ runtime code and we don’t actually care if end users can or can’t re-link to a different version of the noodleglue code. Ho hum…
Tom @ NoodleHeaven