This is now possible with a Gandalf module! See com.netbeans.examples.modules.crosscompile.* in src_examples area in StarTeam. Also note that execution seems to work fine without anything special--i
t looks for the class files, so the filesystem finds them automatically, at least in Gandalf. Only important feature missing is that error expressions must be one of the three standard; you cannot con
figure or save custom expressions. External compile only, of course.

Suggested configuration: on Internal Compiler settings, a pulldown menu "Compile To", with one option "<same filesystem>" (default, behavior as at present), and one option per writable mounted filesys
tem. If a different filesystem was selected, all compilation .class output would be redirected to the file of the same package and name on that filesystem, rather than the filesystem of the source fil
e. Also, isUpToDate must check on a different filesystem. Execution should not be affected, though, as the classloader finds it OK.


Should not be terribly difficult to implement in the JavaCompiler, as there are only a few lines of code that I can see that actually write out the .class. Ditto for ExternalCompiler--it should just a
dd a -d, and modify isUpToDate accordingly, also using the same filesystem pulldown. (ExternalCompiler should also refresh the destination filesystem, because otherwise the right data objects on the d
est fs might not even be created -> classloader for internal execution does not see them, or newer versions might not have been read from disk.)

Many people request this!