> > > > No, my proposal is to add just one more output directory, which all > > non-javac classfile generation tools can target. > > This seems like a really ugly solution. All the classfiles > for package foo.bar should go into a single directory - typically > build/classes/foo/bar. > > Also, consider a hypothetical compiler that can compile multiple > languages, including java, perhaps based on a plug-in architecture. > This would be necessary for allowing mutually dependent classes. > While such a cmpiler is a long way off (though it should be > doable for JavaFX and Java, since both are based on javac), > which shouldn't standardize a broken layout.
Just FYI, Your 'hypothetical compiler' sounds quite a bit like what building with Maven (http://maven.apache.org/) does when compiling joint Java/Groovy projects. (see http://groovy.codehaus.org/GMaven). This type of project allows for mutually dependent classes (Groovy depending on Java and vice versa). Compiled classes ALL go into a single directory (in this case 'target/classes'). Compiled test classes, of course, are kept separate ('target/test-classes') -- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ Brian Schlining [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
