On Fri, 12 May 2006, Steve Loughran <[EMAIL PROTECTED]> wrote: > Prior to ant1.6, the unix model was all that ant had. so it worked > on all non -VMS platforms, and it worked for java apps
Correct, but as you say, this was prior to Ant 1.6. > Then we put that patch from the OpenVMS people that said "here is > the logic to handle VMS return codes", with some other stuff for > execing java apps. I don't know where jdk exes fit in here - I think > they need to be given unix rights. And this is how Ant 1.6 has been treating it. Ant treated jdk executables using the Unix model and only applied the OpenVMS logic for the other executables. > If there are some executables with unix result code logic, and other > bits with VMS rules, then its essentially impossible to > "automatically" make the right decision. > > We could switch to unix-policy-everywhere, with a per-<exec> flip to > VMS if you want run VMS-specific apps. ... and break backwards compatibility with 1.6. I'd rather introduce the flip but make it default to Ant 1.6's behavior. > My concern there is cvs and SVN: what kind of exe are they? I'd expect them to return EXIT_SUCCESS or EXIT_FAILURE which are defined to be 1 and 0 respectively if I recall my OpenVMS C knowledge correctly (which hasn't been used for eight years now). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
