Jess Holle wrote >> Anything developed that 'links' with a GPL can arguably be considered >> a derivative product of it. So, if you build a plug-in on top of a GPL >> program, your plug-in is implicitly GPL as well. That only applies to >> making programs FOR NetBeans, not making programs ON NetBeans. The >> output of GPL applications are not in themselves restricted by >> license. But the thing I don't know is that if the NetBeans >> development API's were released as an open specification (to be >> implemented by any compliant IDE for instance) then you could write >> plug-ins since the plug-in could function without using GPL'd NetBeans >> code. >> > The classpathexception is rather clear on this. Compiling against > NetBeans libraries is not restricted by GPL in this case. > Recompiling/rebuilding existing portions of NetBeans is. > Exactly. The fact that Java itself is licensed in the same way, but the whole world of things built on Java aren't forced to be GPL, should make it even more clear.
-- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [email protected] - mobile: +39 348.150.6941 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
