> > >> Let me try to be a bit more precise here. You can't very well write much >> Java code, without needing to implement an interface or an abstract >> class... or a lot of these actually. The AWT/Swing event system comes to >> mind as one of the most obvious parts of the API where this is true. So >> where would you draw the line... are we only allowed to implement >> interfaces? Extend abstract classes? Where is this stated/formulated?
I didn't even consider this case but I think it's spot on. > > > You can even take OpenJDK, fork it, change the API and redistributed it under > a new name and the same GPL + CPE license. No problems with the copyright, > maybe problems with patents (the old discussion about whether GPLv2 protects > enough or not). Isn't this essentially what google did? -- Kirk -- 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.
