On Fri, Mar 10, 2006 at 11:41:11AM -0600, Archie Cobbs wrote: > Weldon Washburn wrote: > >>Either solution is OK with me, but I'd much prefer #1 because it's > >>cleaner code and I'd rather not start adding hacks at this point that > >>move us away from the current common API. > > > >I agree that #1 is the cleanest, easiest technical approach. The > >difficulty is convincing an attorney that a file in Harmony Class Lib > >called "blah blah GNU blah blah CLASSPATH" has nothing to do with gnu > >or classpath. I vote for adding a few lines of code to avoid spending > >hours with an attorney. > > Hmm.. honestly I'm starting to lose patience with all this legal nonsense. > Not your fault of course Weldon. > > Rhetorically I ask how is using "gnu.classpath" in a class name any worse > than using "java.lang"? Sun has a trademark on the work "java" you know.
Or what about com.sun.* ? You'll have to for the doclets stuff. Honestly, we need to credit lawyers with a little more sense than that. > Can someone (Geir?) give us a quick answer on this so we can proceed?? Yes, please. -- ================================================================ Stephane Meslin-Weber Email: [EMAIL PROTECTED] Senior Software Engineer Web: http://odonata.tangency.co.uk ================================================================
signature.asc
Description: Digital signature
