> > > But the other Runtime.exec() methods (without working directory) > > should all work. > > So let's really treat OpenVMS like OS/2 and disable the Jdk13Launcher > unconditionally. >
The Java CommandLauncher for VMS could catch the IOException with the message "function not implemented" and tell the user to define the required logical. > > There seem to be some other tasks which check the return value of > > Execute#execute() against zero though, including <cvs>, > > <cvstagdiff>, <cvschangelog>, and <javadoc>. Would this change be a > > backward compatibility issue? > > I don't think so. > > Any user task that used the return value of execute would be as broken > on OpenVMS as it ever was, and should continue working where it did > before. All tasks adapted to the new method should work in OpenVMS as > well without seeing any difference elsewhere. > Great. -- knut
