Chas Emerick schrieb: > I'm trying to push for some sanity in how Netbeans works with > dependencies that provide classfiles generated from non-Java-the- > language sources: http://www.netbeans.org/issues/show_bug.cgi?id=152943 > > Some context: we use clojure extensively, which can emit classfiles in > a non-runtime compilation stage. We bundle those classfiles alongside > a bunch of "legacy" classfiles compiled from Java source files as part > of our standard build process. We're trying to streamline all of our > projects and build processes to work with the Netbeans harness, which > has a variety of advantages. However, we're bumping up against the > Netbeans team's insistence that a Java project is functionally limited > to delivering classfiles from Java source files (at least as far as > the IDE editors are concerned, w.r.t. error flagging, etc).
well, why should Netbeans here be better than Eclipse JDT... on the other hand we have no problem with the editor itself for the eclipse plugin, more with the internals of when, what and how to build. > At the moment, their response to this issue is that every JVM language > should have its own project type (with attendant Netbeans plugin) that > can furnish the IDE with whatever information it needs to support > indicating potential compilation problems, method signatures, etc., in > downstream projects. This is proposed instead of simply looking for > utilized classes (regardless of their source) in jars produced by > upstream projects, and ignores the fact that most JVM language > communities simply do not have the resources or wherewithal to > implement full-fledged IDE support. To get this right... I have a java class and this is extended by a groovy class and then this is extended by a java class... and then I need 3 projects for this? That would be really bad and far from how people are using Groovy. They obviously want one project only. Also in this example there is not really any "up" or "down" > I think it would behoove everyone interested in having a minimal level > of IDE support for any JVM language that can emit classfiles to chime > in on this issue, and perhaps vote up the bug I linked to above. Of > course, I'd be interested in hearing any counterpoints, as well. the bug is already closed? bye Jochen -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead (http://groovy.codehaus.org) http://blackdragsview.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
